Anrok MCP integration for AI agents.
Connect AI agents to Anrok through 7 structured actions, including get customer, get product, and list customers. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 7
- 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 Anrok integration exposes
The Anrok Agent App exposes 7 provider-backed actions for finance and data work. Its current contract lets an authorized agent retrieve one anrok customer by customer id, retrieve one anrok product by external id, and list anrok customers with cursor pagination. 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 Anrok account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Anrok capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve one Anrok customer by customer ID.
INPUTS: customerId
get_productREADRetrieve one Anrok product by external ID.
INPUTS: externalId
list_customersREADList Anrok customers with cursor pagination.
INPUTS: cursor / limit
list_filingsREADList Anrok filings with optional cursor pagination and filters.
INPUTS: cursor / limit / filter
list_product_mappingsREADList Product ID mappings for one Anrok integration.
INPUTS: integrationId
list_product_tax_categoriesREADList product tax categories available on the Anrok seller account.
list_transactionsREADList Anrok transactions with optional cursor pagination and filters.
INPUTS: cursor / limit / filter
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
customerIdREQUIRED- The unique customer identifier in Anrok.
get_product
externalIdREQUIRED- The external product ID to look up in Anrok.
list_customers
cursorOPTIONAL- The Anrok cursor returned as nextCursor from the previous page.
limitOPTIONAL- The maximum number of customers to return.
list_filings
cursorOPTIONAL- The Anrok cursor returned as nextCursor from the previous page.
limitOPTIONAL- The maximum number of filings to return.
filterOPTIONAL- The filter to apply to returned filings.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve one Anrok customer by customer ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerVerify with Get Product
Retrieve one Anrok product by external ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_productSAFETY BOUNDARY
Operate Anrok with explicit limits
- Authorize Anrok with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Anrok data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Anrok rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Anrok task completed successfully.
CONNECTION MODEL
API key
Anrok API key sent with the Authorization Bearer header. Create or view API keys in Anrok: https://app.anrok.com/-/api-keys.
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
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Anrok.