API

Three token-gated, CORS-enabled JSON resources — pull RWA Leads intelligence into your own dashboards, CRM or agents. Authenticate with a bearer token.

[00] LEADS

GET /api/v1/leads returns the ranked Lead read model — the same list behind /leads. Add ?format=curioos for CurioOS-shaped rows (source: "signal"), ready to insert into its leads table. Use ?since=<ISO> for incremental pulls. Create a key at /account/keys — it belongs to your account, not a shared env token, and you can revoke it any time. Leads name real people, so the demo token is refused here (403).

curl -H "Authorization: Bearer cs_live_…" \
  "$ORIGIN/api/v1/leads?track=raise&limit=20"

curl -H "Authorization: Bearer cs_live_…" \
  "$ORIGIN/api/v1/leads?format=curioos&since=2026-09-01T00:00:00Z"

[01] RESOURCES

GET /api/v1/leads

Ranked leads — the v4 product

?track=raise|sell ?tier= ?region= ?minScore= ?since= ?q= ?format= ?limit=

GET /api/v1/signals

Scored intent signals

?type= ?region= ?tier= ?minScore= ?q= ?sort= ?limit=

GET /api/v1/entities

Investors, funds & companies with live intent

?kind= ?region= ?stage= ?q= ?limit=

GET /api/v1/events

RWA & tokenization events

?region= ?limit=

[02] AUTH

Pass a bearer token in the Authorization header. Tokens are provisioned in the CURIO_API_TOKENS env var (comma-separated). Until you provision real tokens, a read-only demo token is accepted for signals, events and entities (never for leads):

curl -H "Authorization: Bearer curio_demo_readonly" \
  "$ORIGIN/api/v1/signals?tier=hot&limit=5"

[03] TRY IT

Live against this instance. The demo token is pre-filled.

Resource

Bearer token