quotient-api

Handle 402 payment required responses by detecting the challenge, reading the PAYMENT-REQUIRED details, signing it, then retrying with a PAYMENT-SIGNATURE header and parsing the PAYMENT-RESPONSE. This x402 flow enables monetized access to prediction market data endpoints.

Yes, you can use an API key instead of x402 micropayments for market intelligence requests by including the x-quotient-api-key header. This authorizes monetized requests directly, bypassing the 402 challenge and settle cycle entirely.

Available market intelligence endpoints include tracked markets, mispriced markets, per-market intelligence, analyst signals, and 24-hour narratives with Polymarket links. Retrieve mispriced markets by calling GET /api/v1/markets/mispriced with your configured auth method.

Discovery preflight fetches and caches metadata from /openapi.json and /api/public/pricing, refreshing it periodically. It uses runtime 402 details as the authority, ensuring deterministic preflight and cached pricing metadata for reliable API requests.

Correct retry rules for 429 rate limits and transient 5xx errors are enforced during invocation. The API skill automatically applies these retry rules to ensure reliable access to canonical endpoints for markets, signals, and narratives.

No, you do not need to manually manage the x402 payment flow when fetching 24-hour narratives. The skill automatically handles the required 402 payment challenge, signature, and retry logic, returning the narrative data seamlessly.