Commerce & finance · wired today
Adyen, wired into your agent workforce
Money data demands the strictest governance of anything agents touch. The Adyen connector is one of 222 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
Connecting Adyen takes one credential
You provide API key, merchant account from your Adyen account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Adyen's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Adyen
list_merchantsList the Adyen merchant accounts this API credential can reach (id, name, company, status, capture delay)
get_merchantGet one Adyen merchant account by merchant ID (name, company, status, settlement currency)
list_storesList the stores under one Adyen merchant account (id, description, status, address, merchant reference)
list_payment_methodsList the payment methods configured on one Adyen merchant account, optionally scoped to one store
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
Adyen answers every unauthenticated request identically, so its endpoint paths rest on Adyen's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Read-only It ships read tools only, so there is nothing to approval-gate.
- Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
- Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
- Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.
Adyen integration FAQ
What can Quox agents do with Adyen?
Agents can run 4 read-only tools against Adyen: list merchants, get merchant, list stores, list payment methods. Every call is receipted in the evidence trail.
What does the Adyen integration need?
You provide API key, merchant account from your Adyen account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Adyen credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Adyen connector?
Adyen answers every unauthenticated request identically, so its endpoint paths rest on Adyen's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.