Enigma MCP integration for AI agents.
Connect AI agents to Enigma through 12 structured actions, including create list, create suggestion, delete list, and verify business v2. Review authenticati…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Enigma integration exposes
The Enigma Agent App exposes 12 provider-backed actions for data work. Its current contract lets an authorized agent create a user-managed enigma list from a search definition or input file, with optional aliases, column ordering, and column mapping, submit a suggestion to enigma for data correction or enrichment feedback using the official graphql suggestion mutation, and delete a user-managed enigma list by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Enigma account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Enigma capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_listREADCreate a user-managed Enigma list from a search definition or input file, with optional aliases, column ordering, and column mapping.
INPUTS: name / listType / description / searchInput / fileFormat
create_suggestionWRITESubmit a suggestion to Enigma for data correction or enrichment feedback using the official GraphQL suggestion mutation.
INPUTS: suggestedByEmail / payload / status / suggestedValue / ancestorIdentifier
delete_listHIGH IMPACTDelete a user-managed Enigma list by ID.
INPUTS: id
verify_business_v2REVIEWVerify a business with Enigma's KYB v2 API, returning a normalized risk summary and the raw verification payload.
INPUTS: package / attrs / name / names / tin
get_accountREADRetrieve the current Enigma account metadata available to the connected API key, including customer, billing, and auto-recharge details.
get_aggregate_countsREADRun the official Enigma GraphQL aggregate query to count matching entities or related entities for a search request.
INPUTS: prompt / id / name / address / addresses
get_background_taskREADRetrieve the latest status for an Enigma background task created by an asynchronous GraphQL search or export workflow.
INPUTS: id
get_businessREADRetrieve a single Enigma entity by GraphQL entity ID and entity type, returning the provider entity payload.
INPUTS: id / entityType
get_graphql_schema_extendedREADRetrieve Enigma's extended GraphQL schema metadata, including types, projections, and data-asset descriptors.
get_list_materializationREADRetrieve an Enigma list materialization by ID, including progress, generated resource URI, metrics, and billing details.
INPUTS: id
search_graphqlREADSearch Enigma entities through the official GraphQL search query, supporting direct lookups, structured filters, natural-language prompts, and asynchronous output generation.
INPUTS: prompt / id / name / address / addresses
search_listsREADQuery user-created Enigma lists with optional name or ID filters and Relay-style pagination controls.
INPUTS: id / name / conditions / first / after
INPUT CONTRACTS
Know what the action needs before it runs.
create_list
nameOPTIONAL- The list name to create.
listTypeOPTIONAL- The Enigma list type used when creating or returning a list.
descriptionOPTIONAL- The optional list description.
searchInputOPTIONAL- The official Enigma list search input object.
fileFormatOPTIONAL- The output file format Enigma should use for exports.
create_suggestion
suggestedByEmailOPTIONAL- The email address of the person submitting the suggestion.
payloadOPTIONAL- A loose JSON object.
statusOPTIONAL- The suggestion status to set when supported.
suggestedValueOPTIONAL- The JSON value being proposed for the target field.
ancestorIdentifierOPTIONAL- Ancestor entities related to the suggestion.
delete_list
idOPTIONAL- The Enigma list ID to delete.
verify_business_v2
packageOPTIONAL- The Enigma KYB package to run.
attrsOPTIONAL- Additional KYB attributes to request.
nameOPTIONAL- A business name to verify.
namesOPTIONAL- Up to two business-name candidates to verify.
tinOPTIONAL- A business TIN or EIN to verify.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create List
Create a user-managed Enigma list from a search definition or input file, with optional aliases, column ordering, and column mapping. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_listControl Create Suggestion
Submit a suggestion to Enigma for data correction or enrichment feedback using the official GraphQL suggestion mutation. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_suggestionVerify with Get Account
Retrieve the current Enigma account metadata available to the connected API key, including customer, billing, and auto-recharge details. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_accountSAFETY BOUNDARY
Operate Enigma with explicit limits
- Authorize Enigma with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_list` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Enigma rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Enigma task completed successfully.
CONNECTION MODEL
API key
Enigma API key sent with the x-api-key header. Create it from the Enigma API getting-started flow: https://developers.enigma.com/docs/getting-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Enigma.