Skip to main content
These docs are built so coding agents can read them. Give your agent the context below, and it can write a working Zapyd integration with the correct signing, base URLs and request bodies.

​
Machine-readable docs

Every page also has a copy menu at the top. Use it to copy the page as Markdown, or to open it in ChatGPT, Claude, Perplexity, Cursor or VS Code.

​
Docs MCP server

The MCP server lets your agent search these docs while it works, so it doesn’t rely on stale training data.

​
Integration prompt

Copy this into your agent to start an integration. Each endpoint page in the API reference also has its own prompt with the exact URL and signing rules.

Integrate Zapyd payouts

Open in Cursor

​
Tips for agent-written integrations

  • Check the signature first. Have the agent write a unit test for the test vector before anything else. Most failed integrations are signing bugs.
  • Keep the agent on sandbox. Give it only sandbox credentials. Use the mock status endpoints so it can test every final status.
  • Point it at the spec for types. The OpenAPI file lists every required field and enum. Agents that read it make fewer validation mistakes than agents that guess from examples.
  • Review money paths yourself. Read the code that moves funds, handles webhooks and retries orders yourself. Don’t rely only on agent-written tests.