Migration Guide

If you already call Polymarket (or other sources) directly, you can replace many integrations with one POST to Falcon and use agent_id to pick the dataset. See API structure and Core concepts for request shape and field rules.

Why migrate?

One endpoint, all platforms

Stop maintaining separate integrations for Polymarket, Kalshi, and social data.

No rate limit management

Falcon handles upstream rate limits so you are not throttled at the source.

Enriched data

Get computed metrics (F-Score, Wallet 360, Market 360) that the source APIs do not expose.

Sub-300ms latency

Consistent, cached-backed responses for interactive workloads and pipelines.

From Polymarket API

Polymarket endpoint	Falcon equivalent	`agent_id`
`GET /markets`	Polymarket Markets	`574`
`GET /trades`	Polymarket Trades	`556`
`GET /prices/history`	Candlesticks	`568`
`GET /book`	Orderbook	`572`
(not available on source API)	Wallet 360	`581`
(not available on source API)	Falcon Leaderboard (F-Score)	`584`
(not available on source API)	Price jumps	`596`
(not available on source API)	Market 360	`575`

Before vs after

Direct CLOB call vs the unified parameterized retrieve URL used everywhere in this docs set (API structure):

GET https://clob.polymarket.com/markets?closed=false&limit=10

Headers:
  (Polymarket / wallet headers as required by the CLOB)

POST https://narrative.agent.heisenberg.so/api/v2/semantic/retrieve/parameterized
Content-Type: application/json
Authorization: Bearer YOUR_TOKEN

{
  "agent_id": 574,
  "params": {
    "closed": "False"
  },
  "pagination": {
    "limit": 10
  }
}

From Kalshi API

Kalshi endpoint	Falcon equivalent	`agent_id`
`GET /markets`	Kalshi Markets	`565`
`GET /markets/trades`	Kalshi Trades	`573`

Key differences to note

Single POST endpoint
Falcon uses one URL for everything. The agent_id in the request body replaces different source URL paths.
All params are strings
Unlike some source APIs that accept mixed types, Falcon params values are always string values, for example "1000", not 1000. See API structure.
Unified pagination
Every dataset uses the same limit / offset / has_more pattern—no per-endpoint cursor gotchas. See API structure.
Bearer token auth
A single Authorization: Bearer header replaces per-platform auth schemes. See Authentication.

Overview

Composite workflows

Polymarket

Kalshi

Social Intelligence

Migration Guide

Why migrate?

One endpoint, all platforms

No rate limit management

Enriched data

Sub-300ms latency

From Polymarket API

Before vs after

From Kalshi API

Key differences to note

​Why migrate?

One endpoint, all platforms

No rate limit management

Enriched data

Sub-300ms latency

​From Polymarket API

​Before vs after

​From Kalshi API

​Key differences to note

Why migrate?

From Polymarket API

Before vs after

From Kalshi API

Key differences to note