Adyen MCP integration for AI agents.
Connect AI agents to Adyen through 6 structured actions, including get api credential, get company, and get merchant. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 6
- 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 Adyen integration exposes
The Adyen Agent App exposes 6 provider-backed actions for finance work. Its current contract lets an authorized agent retrieve details for the adyen api credential used by this connection, retrieve one adyen company account by id, and retrieve one adyen merchant account 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 Adyen account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Adyen capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_credentialREADRetrieve details for the Adyen API credential used by this connection.
get_companyREADRetrieve one Adyen company account by ID.
INPUTS: companyId
get_merchantREADRetrieve one Adyen merchant account by ID.
INPUTS: merchantId
list_companiesREADList Adyen company accounts accessible to the API credential.
INPUTS: pageNumber / pageSize
list_company_merchantsREADList merchant accounts under an Adyen company account.
INPUTS: companyId / pageNumber / pageSize
list_merchantsREADList Adyen merchant accounts accessible to the API credential.
INPUTS: pageNumber / pageSize
INPUT CONTRACTS
Know what the action needs before it runs.
get_company
companyIdREQUIRED- An Adyen resource identifier.
get_merchant
merchantIdREQUIRED- An Adyen resource identifier.
list_companies
pageNumberOPTIONAL- The page number to fetch from Adyen.
pageSizeOPTIONAL- The number of items to include on one page.
list_company_merchants
companyIdREQUIRED- An Adyen resource identifier.
pageNumberOPTIONAL- The page number to fetch from Adyen.
pageSizeOPTIONAL- The number of items to include on one page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Credential
Retrieve details for the Adyen API credential used by this connection. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_credentialVerify with Get Company
Retrieve one Adyen company account by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_companySAFETY BOUNDARY
Operate Adyen with explicit limits
- Authorize Adyen with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Adyen 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.
- The sampled contract declares provider scopes including `Management API—Account read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Adyen task completed successfully.
CONNECTION MODEL
API key
Adyen Management API key sent in the X-API-Key header. Generate or view API keys in your Adyen Customer Area: https://docs.adyen.com/development-resources/api-credentials#generate-api-key
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
- 6
- 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 Adyen.