Account access
Open your API-plan account.
Sign in with email and password after claiming your checkout email. The emailed API key remains the machine credential; the browser portal can bind through the one-use claim link for billing, usage, receipts, and account review.
- First claim
- Use the one-use claim link from checkout, then sign in by email and password.
- API routes
- x-market-state-api-key stays supported
- Account routes
- session cookie plus CSRF for billing and portal actions
- Billing
- Stripe Customer Portal for plan management
Reset tokens are delivered by email and do not return or rotate your API key.
Customer portal
Operate paid market-state features.
Quality, calibration, and price-action QA
Track QA evidence for packet labels, replay, calibration, routes, exports, and same-symbol price-action markouts without treating the readout as a trading-performance claim.
Latency budget from this browser session
Route timings are measured locally as this portal loads paid modules. Heavy packet reads are expected to be reviewable, but budget misses should be visible before they become integration friction.
Read, inspect, replay, route, and measure one packet
Start with one current market-state packet, then widen symbols, routes, exports, or usage after the loop is visible.
Confirm the session before testing a tier.
If this does not match the latest checkout email or key, switch key and claim the newest emailed API key.
Open the Monitor shell with this account context
Session summary only: saved layout state stays in this browser and does not mutate account configuration.
Operate the account loop
Live access, calibration, and upgrade boundary
Account scope and next action
Credit burn and receipt trail
Run paid review, replay, and brief routes
Register and verify webhook routes
Create and evaluate packet rules
Create review packs and retained export jobs
Recent metered account activity
Developer payload Latest account response
{}