Racing OS Pro
How Racing OS Pro Works
A clear, structured workflow from input to insight. Six steps that cover everything from authentication to session verification.
Authenticate
Start by authenticating with your wallet address or obtaining a guest session token. Authentication returns a Bearer token that identifies your client account and links your session to your plan and balance.
Run an Engine
Submit a race identifier to one or more analytical engines. Each engine processes the normalised race data and returns structured output. You can run engines individually or use the combined endpoint to run all four in a single call.
Generate Formcards
Request a formcard for a race. The formcard pipeline fetches, normalises, and assembles race data — runners, form history, timeline, and statistics — into a single canonical document ready for analysis or downstream use.
Manage Billing
Review your billing cycle, check your current plan, and manage your subscription via the billing endpoints. Upgrade, downgrade, cancel, or renew your plan at any time. Your SWTT allocation resets at the start of each billing cycle.
Read Token-Linked State
The SWTT read-only endpoints let you monitor token-linked state on Base Mainnet — balance, recent transfer events, token information, and total supply. These endpoints are read-only and do not affect your session or billing state.
Verify Sessions
The TAP session endpoints allow you to look up and verify session identifiers. Session lookup checks whether a session exists in the ledger. Verification confirms session validity at a high level without exposing protocol internals.
Ready to get started?
Review the API documentation or choose a plan.