AI & Agent Policy
Last updated: April 2026
This page describes how AI agents, automated clients, and crawlers should interact with PolyTrackers. For the machine-readable version see /llms.txt. For full API reference see /docs/api.
Authenticate with an Agent API Key
If you are an autonomous or AI-powered client doing anything beyond reading public marketing pages, authenticate with an Agent API Key. Session scraping from a headless browser is challenged by bot detection and is not a supported access pattern.
Agent API Keys are prefixed ptk_ and must be sent as Authorization: Bearer ptk_…. Scopes (signals:read, agent:scan, agent:full) are listed in the API docs.
Always-open lanes
These paths are unconditionally available to automated clients without an Agent API Key: /api/openapi.json, /api/public/**, /api/webhooks/**, /api/mcp*, /llms.txt, /robots.txt, /sitemap.xml.
Alchemy and Stripe webhook paths are similarly open but validate their own signatures — do not send requests there without a valid payload.
Rate limits
All authenticated endpoints are rate-limited per user, per Agent API Key, and per IP. Rate-limit tiers, 429 response shapes, and the Idempotency-Key contract for /api/trade/execute are documented in the API docs.
Respect Retry-After headers. Requests that continuously ignore 429 responses will be blocked at the firewall level.
Verified crawlers
We allowlist Vercel-verified crawlers (GPTBot, ClaudeBot, PerplexityBot, Googlebot, Bingbot, and others) to index our public pages unimpeded. That allowlist does not extend to custom agents built on the OpenAI or Anthropic SDKs — those must authenticate with an Agent API Key.
Training & crawling policy
Public marketing pages (/, /pricing, /docs/**, /blog/**) may be crawled and cited.
Dashboard pages, user data, and anything behind a session are off-limits for training corpora.
Do not scrape Polymarket data through our session endpoints. Use the Agent API Key lane and the documented endpoints instead.
Machine-readable version
A machine-readable version of this policy — optimised for AI agents and automated clients — is available at /llms.txt. That file is the authoritative source for endpoint lists, error shapes, and rate-limit summaries.
Contact
Questions about automated access, Agent API Key scopes, or abuse reports: support@polytrackers.com.

