Docs
Build against Apipunt.
Start here if you are a human developer, local agent, or coding assistant integrating subscription-gated racing tips and Telegram control flows.
Agent quick start
1. ReadFetch /agents.json for canonical agent instructions, source aliases, auth rules, and recommended first calls.2. InspectFetch /openapi.json for route structure, then use /llms.txt for compact model context.3. AuthenticateUse X-API-Key for production requests. Query-string keys are only for browser demos.4. Pull tipsCall /v1/tips by date, source, or rolling day window. Add include_runner=true for PFAPI field context.5. ControlUse /signup email in Telegram for new users, or /link for existing users, so they can call tips from the bot and later approve bet execution.curl 'https://api.apipunt.com/v1/tips?source=tw&days=10' -H 'X-API-Key: $APIPUNT_KEY'
Response envelope
Most API responses return JSON as { "data": ... }. Agents should treat missing optional fields as unavailable data, not as errors.