API reference
Two surfaces, one core.
Pay By AI exposes the same operations through two transports. Traditional backends and plugins use the REST API. AI agents use the MCP (Model Context Protocol) endpoint. Both call into the same business logic, so feature parity is an invariant — if something works on one surface, it works on the other.
REST API
HTTPS + JSON for backends.
For merchant backends, e-commerce plugins, CLI tools, and any non-AI integrator. Authenticate with your merchant API key; mint payment tokens; cancel; read.
https://www.paybymyai.com/api/*
MCP API
JSON-RPC tools for AI agents.
For Claude, ChatGPT, and custom agents. Authenticate with a budget code the user minted. Discover merchants, preview tokens, pay — bounded by the user's consent rules.
POST https://www.paybymyai.com/api/mcp
Machine-readable summary
For AI clients ingesting the API from a short file, we follow the llmstxt.org convention:
/llms.txtOther docs in this site
- Customer setup — sign in, add a card, connect an AI, create a budget.
- Merchant setup — Stripe Connect onboarding, API key, webhook verification.