Parameters & Limits

Time windows

Many endpoints accept time window parameters to control the lookback period.

`since` parameter

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

`hours` parameter

Shorthand for since. Pass an integer number of hours.

GET /v1/follows/new?hours=48
# equivalent to: GET /v1/follows/new?since=48h

If both since and hours are provided, since takes priority.

Defaults by endpoint

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

Invalid values

If the time parameter can't be parsed, the API returns:

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

Result limits

Endpoint	Default	Max
`GET /v1/search`	50	200
`GET /v1/trending`	25	100
`GET /v1/feed`	50	200
`GET /v1/discover`	20	50
`GET /v1/vc/:handle/similar`	20	50

Other endpoints return all matching results within the time window.

Filtering

Enriched follows filters

GET /v1/follows/enriched supports filtering results by classification:

Parameter	Example	Description
`sector`	`?sector=DeFi`	Filter by sector (substring match)
`keyword`	`?keyword=stablecoin`	Search username, name, description, sector
`entity_type`	`?entity_type=company`	Filter by entity type
`tag`	`?tag=my-custom-tag`	Filter by custom tag or rule name

Feed filters

Parameter	Values	Description
`event_type`	`new_follow`, `convergence`	Filter by event type
`sector`	Any sector string	Filter targets by sector

Discover filters

Parameter	Default	Description
`sector`	-	Narrow by sector
`min_signal`	`0.3`	Minimum signal score (0.0 - 1.0)

Classification

AI classification

Several endpoints return classification data:

Field	Values	Description
`sector`	DeFi, AI, Infrastructure, Gaming, Trading, Payments, etc.	Primary sector
`entity_type`	company, project, person, fund, vc	Entity classification
`is_company`	true/false	Whether entity is an organization
`confidence`	high, medium, low	Classification confidence

Classification is probabilistic. For workflows requiring stable labels, query once and cache.

Custom classification rules

Create custom rules via POST /v1/classify/rules to tag entities matching your criteria. These rules are applied automatically in /v1/follows/enriched and /v1/discover responses.

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 daily
Classification: Cached server-side, refreshed periodically
Company intelligence: Fetched on-demand, with upstream caching (60 min Twitter, 2 hr scrape, 24 hr LinkedIn)

Cost tracking

Every charged response includes cost and balance fields:

{
  "data": [...],
  "cost_cents": 10,
  "balance_cents": 9890
}

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

Pricing Errors & Status Codes