Was this page helpful?
Attribution.ai supports OAuth + PKCE for connector flows and bearer tokens for direct MCP requests.
Use OAuth for ChatGPT, Claude, and Gemini connector onboarding. Discovery and token endpoints:
/.well-known/oauth-authorization-server/.well-known/oauth-protected-resourcePOST /api/mcp/authorizePOST /api/mcp/tokenPOST /api/mcp/registerGenerate API keys from Connect Your AI in the dashboard. Keys are scoped to a brand/workspace and are shown once at creation.
curl -X POST https://attribution.ai/api/mcp/rpc \
-H "Content-Type: application/json" \
-H "Authorization: Bearer atai_your_key_here" \
-d'{"jsonrpc":"2.0","method":"tools/list","id":1}'The Attribution AI CLI supports OAuth login, service keys, and API keys:
# Browser OAuth (recommended for humans) attribution auth login # Service key (recommended for automation) attribution auth login --service-key atai_svc_xxx # API key env fallback export ATTRIBUTION_API_KEY="atai_your_key_here" attribution tools list
Credential priority: --service-key / --api-key flag > env vars > saved OAuth session.
MCP limits are enforced per minute and are calculated from monthly order volume:
| Monthly Orders | Rate / Minute | Notes |
|---|---|---|
| 1 - 5,000 | 10 | Default baseline |
| 5,001 - 25,000 | 60 | Higher throughput for growing stores |
| 25,001+ | 300 | High-volume stores |
When rate limited, the API returns HTTP 429 with JSON-RPC error data that includes current usage and your current per-minute rate.
Keep your keys safe