API and data

Public reads

GET /api/economics returns the current official economics, the source timestamp and whether the snapshot is stale. GET /api/assets?q= searches indexed assets on Robinhood. GET /api/projects lists confirmed Pair launches with a next-page cursor.

Requests are rate limited. A provider outage returns an error or a truthfully aged cached snapshot; it is not represented as a successful empty result.

curl https://pair.trade/api/economics
curl "https://pair.trade/api/assets?q=cashcat"
curl https://pair.trade/api/projects

Freshness and cost

Reusable economics are cached for one minute; asset search is cached for five minutes. Maximum fallback ages are five and thirty minutes respectively. Concurrent refreshes share a PostgreSQL lease so multiple visitors do not trigger duplicate provider work.

Browse refreshes are demand driven. When no one requests the data, the application does not keep refreshing it. Transaction simulation and ownership checks use fresh chain reads instead of treating market-cache data as an execution guarantee.

Authenticated operations

Privy verifies your sign-in, and Pair checks that the selected wallet belongs to your Privy account before creating a short-lived, HTTP-only session. Uploads and launch preparation require this session and the expected request origin. The session does not authorize spending; wallet transactions still need a signature.

POST /api/launch/prepare prepares and simulates a launch. POST /api/launch/submit binds a submitted hash to that reviewed transaction. GET /api/launch/status checks its receipt. These endpoints are the application workflow and are not an unrestricted relayer.

Limits and errors

Use short queries, bounded page sizes and the returned cursor. Respect HTTP 429 and Retry-After rather than retrying continuously. HTTP 503 means a dependency or configuration is unavailable.

The asset-search API is an indexed search, not a complete ranking of every token. External metadata cannot prove token safety or transfer compatibility.