Developers
HTTP API.
PayAI is a product with HTTP endpoints, not a published SDK. Some routes are public on purpose. Most dashboard writes use your session. This page lists the ones you can actually call without pretending the rest is a stable public API.
Last updated 20 September 2026
01What this is
The dashboard talks to /api/* with a session cookie. That is first-party, not a partner integration. If you are building against PayAI from another service, start with the public GET routes and the merchant key — and expect the surface to evolve.
02Public GET endpoints
| Method | Path | What it returns |
|---|---|---|
| GET | /api/fees | Current platform fee rates per feature |
| GET | /api/onchain | Live contract addresses |
| GET | /api/automation-config | Executor, vault, WMON, USDC addresses |
| GET | /api/health | Liveness — connected or not. No model, no balances |
| GET | /api/tokens | Verified token list, or resolve an address |
/api/tokens?address=0x… reads arbitrary contracts and is rate-limited./api/health does not expose the agent wallet address or its balance.
03Merchant key
POST /api/merchants creates a workspace and returns an API key once. Send it as x-merchant-key on later merchant-scoped calls (for example payment links). The key is not recoverable from the API after that response.
04What is not a public API
Automations, Ask PayAI, swaps, and anything that can move funds are session-authenticated dashboard routes, or gated on an internal signer key that is not issued to third parties. Treat them as the app backend.
Contracts you can verify: Contracts.