AArtery
WelcomeGet StartedConceptsProvidersRecipesReferenceAPI ReferencePlayground
On this page

Quick Start

  1. Create an API key

    Artery API keys are scoped (read / trade / stream) and tier-based (free / builder / pro / enterprise).

    bashcurl -X POST https://api.artery.questflow.ai/keys \
  -H "Content-Type: application/json" \
  -d '{"name":"my-bot","userId":"u-1","scopes":["read"]}'

    The response includes a plaintext token of the form art_live_<id>.<secret>. Copy it now — it will not be shown again.

  2. List markets across providers

    Every data endpoint accepts the same Bearer token shape:

    bashTOKEN="art_live_..."
 
curl "https://api.artery.questflow.ai/v1/polymarket/markets?active=true&limit=5" \
  -H "Authorization: Bearer $TOKEN"
 
curl "https://api.artery.questflow.ai/v1/kalshi/exchange/status" \
  -H "Authorization: Bearer $TOKEN"
 
curl "https://api.artery.questflow.ai/v1/hyperliquid/info/meta" \
  -H "Authorization: Bearer $TOKEN"
  3. Inspect the wire format

    Every response is { native, meta }. The upstream raw shape lives in native; meta carries provider name, fetch timestamp, and source (live / indexed):

    json{
  "native": [ /* Polymarket Gamma JSON */ ],
  "meta": {
    "provider": "polymarket",
    "fetchedAt": "2026-05-05T07:30:00.000Z",
    "source": "live"
  }
}
    Note

    A future release will add an optional normalized field on responses where semantics align across providers. The native shape is preserved indefinitely.

  4. Browse the live API reference

    Open api.artery.questflow.ai/docs for a Swagger UI you can call directly with your token.

What's next

Authentication

Bearer tokens, scopes, and rate limits

Providers

Per-platform endpoint catalogs

Streaming

WebSocket subscriptions across all providers

Cross-platform arbitrage

Recipe: monitor Polymarket vs Kalshi spreads

Edit this page on GitHubLast updated
PreviousAuthenticationNextError Handling
Quick Start · Artery API Docs