Let your coding agent build the integration
Point Cursor, Claude Code, Codex, or any coding agent at the Made Card docs. Everything it needs is published as plain markdown and OpenAPI, with the rules it must follow.
Paste this prompt
Integrate my app with the Made Card Partners API. Spec: https://api.madecard.com/partners/openapi.json Guide: https://api.madecard.com/partners/llms-full.txt Follow the "For AI agents" rules exactly. Keep client_secret, the partner JWT, and every link_ token on the server. Build: a server route that creates a link session, a page that loads Made Link and opens it from a button, a server route that exchanges the public_token and stores the access_token, and a route that returns a launch URL. Use environment variables MADE_API_BASE, MADE_CLIENT_ID, MADE_CLIENT_SECRET.
Machine-readable docs
- llms.txtAn index of every guide, in the llms.txt format agents look for first.
/partners/llms.txt - Full guideEvery guide in one markdown file, ready to drop into an agent's context.
/partners/llms-full.txt - OpenAPI specEvery partner endpoint, request, response, and error code.
/partners/openapi.json - Agent guideThe ten-step call sequence, the rules, and a starter Node server.
/partners/docs/ai-agents.md
Rules your agent must follow
Secrets stay on the server
Never put client_secret, the partner JWT, or a link_ token in a browser or mobile app.
The customer token goes in the body
The link_ access token is a JSON field, never an Authorization header.
Apply for new customers, launch for returning ones
Use kind "apply" once. Later visits get a launch URL, not a new session.
Nothing here moves money
Payments and account changes happen in Made Card. There is no endpoint for them.
The full list is in the agent guide.