Authentication
Every request carries one of two credentials: an API key or an OAuth sign-in. Both belong to your account and share its limits.
| API key | OAuth sign-in | |
|---|---|---|
| REST | The Authorization: Bearer header | Not available |
| MCP, remote URL | The same header | Sign in through the browser (the default) |
| MCP, local server | The key in the server’s config | Not available |
API keys
One bearer header on every request. Sign up free (no card) and create a key in API keys. MCP takes the same key, as this header or in the local server’s config (MCP).
The header
Authorization: Bearer YOUR_KEYRequests without this header return 401 Unauthorized. Invalid keys return 401 with { "error": "unauthenticated", "message": "...", "request_id": "req_..." } in the response body.
Verify it with a screen
curl -X POST "https://api.tickerbot.io/v2/scan" \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"q": "pe_ratio < 15 AND earnings_growth_yoy_pct > 15 AND market_cap > 1e9",
"limit": 5
}'A 200 indicates the key is valid; 401 indicates the key is missing or invalid. On writes, a 403 means your account can’t make that change (Errors).
OAuth sign-in
MCP only. Your agent opens a browser, you sign in and approve the connection, and we create a key for that connection. Setup instructions are on the MCP page.
Managing access
Revoke a key in API keys: requests using it return 401 within five minutes. Disconnect an agent in Connected apps.
Limits are per account, not per key: every key and connection shares one per-minute window (Rate limits).