Connect API key and REST
Your own code or any agent without OAuth: a personal API key, on the REST API or the MCP server.
API key and REST
Sign-in: personal API keyYour own code or any agent without OAuth: a personal API key, on the REST API or the MCP server.
1. Create a key
Your API key: the account owner creates it in the dashboard under Connections, New API key. It is shown once; keep it secret. It works only for that account, within its budget frame and approval threshold, and you can revoke it at any time.
2. Use it on the MCP server
Any MCP client that can send a header: the server URL and the header Authorization: Bearer followed by your key.
3. Or call the REST API
Base URL:
curl -H "Authorization: Bearer YOUR_API_KEY" \ "https://api.buzzdealer.ai/v1/publications?region=UK&limit=5"
- Every endpoint is in the OpenAPI document; the tools are listed in llms.txt and on the tools page.
- POST /v1/orders takes an Idempotency-Key header, so a retry never places the same order twice.
- Rate limits per key: reading and ordering each have a limit per minute; over a limit the answer is 429 with retry-after.
- Errors are JSON with error, message and next_step. A revoked key answers 401 with error key_revoked.
After we add new options, disconnect and reconnect the connector so your AI app sees them.
Other clients: Claude, ChatGPT, Cursor, VS Code, Grok, Gemini, Perplexity, Manus, Lindy, Genspark, Devin, Meta Muse, OpenClaw, Hermes.
