Parameters & Limits

Time windows (`since`)

Many endpoints accept a since parameter to control the lookback window.

Supported formats

Format	Example	Description
Hours	`since=24h`	Last 24 hours
Days	`since=7d`	Last 7 days
ISO date	`since=2026-03-01`	Since specific date
ISO datetime	`since=2026-03-01T00:00:00Z`	Since specific timestamp

Defaults by endpoint

Endpoint	Default `since`
`GET /v1/follows/new`	`24h`
`GET /v1/follows/enriched`	`24h`
`GET /v1/convergence`	`7d`
`GET /v1/trending`	`7d`
`GET /v1/vc/:username/activity`	`30d`

Invalid values

If since can't be parsed, the API returns:

{ "error": "Invalid \"since\" parameter. Use \"24h\", \"7d\", or \"YYYY-MM-DD\"." }

Result limits

Some endpoints accept a limit parameter to cap the number of results.

Endpoint	Default	Max
`GET /v1/search`	50	200
`GET /v1/trending`	25	100

Other endpoints return all matching results within the time window.

Classification add-on (`classify`)

Several endpoints accept ?classify=true to enrich results with AI classification:

GET /v1/follows/new?classify=true
GET /v1/follows/enriched?classify=true
GET /v1/convergence?classify=true

Classification costs an additional $0.03 per entity on top of the base operation cost. Classification is probabilistic — each result includes a confidence score (0–1).

Deterministic vs. probabilistic data

Data type	Deterministic?	Notes
Follow events	Yes	Exact graph data — who followed whom, when
Follow counts	Yes	Precise follower/following counts
Convergence	Yes	Exact count of tracked accounts following an entity
Trending rank	Yes	Based on follow velocity over the time window
Classification (sector, entity_type)	No	AI-assigned, includes `confidence` score
Classification (tags, labels)	No	May change if models are updated or new data arrives

For workflows that require stable classifications, query once and cache the result. Classifications for the same entity are cached server-side and reused within a session.

Data freshness

Follow data is updated periodically through the processing pipeline. The API serves the latest processed data, not live fetches.

New follows: Detected within hours of the actual follow event
Tracked accounts: Baseline established on first track, then monitored continuously
Classification: Runs on-demand when classify=true is passed, results cached

If an account was just added via POST /v1/track, allow time for the initial baseline to be established before querying follows.

Cost tracking

Every charged response includes cost and balance fields:

{
  "data": [...],
  "cost_cents": 5,
  "balance_cents": 495
}

Use GET /v1/status to check your current balance, daily spend, and usage breakdown at any time (free, no charge).

Errors Rate Limits