Use this to read published Quotient signals. Sports signals return one game-level pick and markets[] with every linked venue listing, its signal_side, price, and availability. No venue is primary or preferred. Missing quotes do not hide listings. Venue filters find games available there and retain all listings. Non-sports signals retain their market, pricing, and lifecycle fields.
https://quotient-api-gateway.onrender.comUse this to read published Quotient signals. Sports signals return one game-level pick and markets[] with every linked venue listing, its signal_side, price, and availability. No venue is primary or preferred. Missing quotes do not hide listings. Venue filters find games available there and retain all listings. Non-sports signals retain their market, pricing, and lifecycle fields.
Use this to fetch full Quotient intelligence for up to ten markets across Polymarket International, Polymarket US, Kalshi, and HL Outcomes. Returns forecasts, theses, cited drivers, resolution pathways, venue odds, and quote provenance. Polymarket International and Kalshi fail closed when live pricing is unavailable. Prefer market_keys; legacy slugs and condition IDs default to Polymarket unless venue is supplied.
Use this to read Quotient's featured signal, or null. A sports signal returns one game-level pick and markets[] with every linked venue listing; no venue is primary or preferred. Each listing has its own signal_side, price, and availability. Non-sports signals retain their market and pricing fields.
Use this to browse every prediction market Quotient tracks across Polymarket International, Polymarket US, Kalshi, and HL Outcomes, with venue odds and quote provenance, available volume, resolution date, and forecast recency. Polymarket International and Kalshi fail closed when live pricing is unavailable; other venues label graph snapshots stale. Filter by venue or topic; the complete covered catalog returns in one response.
Use this endpoint to read calibrated asset price outlooks across equities, crypto, and commodities, grouped by settlement source and horizon. Each returns five scenarios plus a labeled whole-curve directional take. The nearest still-open horizon is marked without hiding neutral views. A PriceSignal is a separate current execution call and appears only on its exact Hyperliquid group.
Use this to rank covered markets where Quotient's probability differs from a verified live venue quote. The endpoint batches live reads, then applies the odds band, spread threshold, direction, and sort to one selected quote. Missing, stale, and unsupported live quotes are excluded. Returns quote provenance, routing, Q probability, spread, thesis, and venue-reported volume.
Use this to search market titles plus the latest Q summary for a shortlist of recent, open contracts. Returns 10 results by default, at most 20. Use direct topic keywords. Useful alternate angles may use focused searches within a 10-second discovery budget. On a timeout, return candidates already found instead of retrying. Use explicit as_of only for historical questions. Search does not expand graph relationships or run embedding search.
Use this to resolve companies, commodities, cryptoassets, and other underlyings by name, ticker, canonical key, UUID, platform identifier, or linked-market reference. Exact-reference results return every active directly linked market with quote provenance, Q's latest probability and paired thesis, and publication availability. Text results summarize those markets. Probabilities and theses remain tied to their exact questions.
Browse Quotient's canonical underlying-asset directory without forecast or venue-price data. Use this for stable Asset UUIDs and assetKey values, names, tickers, aliases, exact platform identifiers, and active directly linked market counts. The complete filtered catalog returns in one response; use asset search when the user needs linked prediction-market intelligence.
The news and X/Twitter evidence behind Quotient forecasts on Polymarket International, Polymarket US, Kalshi, and HL Outcomes: recent articles and relevant posts for up to ten markets, with reasoning, evidence quotes, source tiers, authors, and canonical routing. Prefer market_keys for cross-venue or nullable-slug rows. Use this to audit a forecast or see what is moving event and asset-linked markets.
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the native x402 API at: https://quotient-api-gateway.onrender.com ** Payment method ** This endpoint is hosted outside FluxA and is called directly, not through the FluxA proxy. It settles on-chain in USDC via x402. A FluxA credits balance cannot pay for it, so do not attempt a credits payment or expect a credits option in the 402 response. Follow the steps below in order. ** Step 1 - Install FluxA Wallet CLI ** npm install -g @fluxa-pay/fluxa-wallet Or use without installing: npx fluxa-wallet <command> ** Step 2 - Register agent ** fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>" The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser. Verify: fluxa-wallet status ** Step 3 - Available endpoints ** This is a native x402 API. The known endpoints are: ** Step 4 - Create an intent mandate ** x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits. Payment is in on-chain USDC. Amounts are in atomic units (6 decimals, e.g., 100000 = 0.10 USDC). fluxa-wallet mandate-create \ --desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \ --amount <BUDGET_IN_ATOMIC_UNITS> \ --seconds <DURATION_IN_SECONDS> Options: - --desc (required): Human-readable spending plan description - --amount (required): Budget in USDC atomic units (6 decimals) - --seconds (optional, default 28800 = 8h): Duration in seconds ** Step 5 - Get user to sign the mandate ** The response from Step 4 includes mandateId and authorizationUrl (TTL: 10 minutes). Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser. ** Step 6 - Wait for mandate to be signed ** fluxa-wallet mandate-status --id <MANDATE_ID> Poll until mandate.status is "signed". The response also includes remainingAmount. Important: Use --id, not --mandate. ** Step 7 - Call the API ** Make the API request to the endpoint URL. If it returns HTTP 402, continue to Step 8. ** Step 8 - Pay via x402 v3 ** Pass the complete HTTP 402 response body as --payload: fluxa-wallet x402-v3 \ --mandate <MANDATE_ID> \ --payload '$PAYLOAD_402' The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON. The response includes xPaymentB64 (the payment token). ** Step 9 - Retry with payment token ** curl -H "Payment-Signature: <xPaymentB64>" <ORIGINAL_API_URL> Return the raw API response to the user without post-processing. ** Opening links for user ** Whenever you need to open a URL (authorization, approval, or any external link): 1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool) 2. Options: [Yes, open the link] [No, don't open] 3. If YES: run 'open "<URL>"' to open in their default browser 4. If NO: ask how they would like to proceed ** Error handling ** - mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl - mandate_expired: Time window passed - create a new mandate - mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit - agent_not_registered: No Agent ID - run 'fluxa-wallet init' first - Invalid payload: missing accepts array: Pass the full 402 response JSON