Enriched new follows
Changed onThe most capable follow-signal endpoint: new follows with AI classification plus your custom classification rules and custom tags merged into each result, filterable by sector, keyword, entity type, or custom tag. Results include people as well as companies; for startup sourcing pass entity_type=company. Same 16-credit price as /follows/new, so use this whenever you want filtered results (e.g. sector=AI follows from the last 7d). Filters are substring matches; valid sector strings can be discovered via /sectors. On a new or thin account (account keys only; fewer than 10 of your own follows in the window, first page at offset 0, no cursor, no username filter) the response also carries starter_companies: companies from your 30-day starter set in your sectors, each with source "starter", filtered by the same sector and keyword, plus a starter_note. Never mixed into results. They come from the whole Frontrun network, not from accounts you track, and stop appearing once your own window fills.
Request
- Base URL: https://frontrun.vc/v1
- URL: https://frontrun.vc/v1/follows/enriched
- Auth: API key in header X-API-Key
Query parameters
Time window: relative ("24h", "7d") or absolute date ("YYYY-MM-DD"). Default "24h".
Alternative to since - window size in hours (e.g. hours=48 equals since=48h).
Restrict to a single tracked account.
Filter by classified sector (substring match).
Filter by keyword across username, name, description, and sector.
Filter by entity type (substring match). Use "company" to drop people and keep only companies: the recommended setting for startup sourcing.
Filter by your custom tag / matched rule name.
Pagination offset (default 0).
Maximum results to return (default 50, max 200).
Opaque watermark from a previous response's next_cursor. Resumes exactly where that run stopped, so a scheduled job that retries neither double counts nor drops records. Overrides since when present. Cursors are signed and scoped to the endpoint, API key and filters; a modified or cross-scope cursor returns 400 with error_code invalid_cursor. Persist next_cursor only AFTER you have processed the response.
Whose follows to read: tracked (default, your tracked accounts), network (the whole Frontrun network; paid Pro and Enterprise) or list:<id> (one of your lists, with its sectors). See /docs/reference/scopes.
Response
Enriched new follows grouped by tracked account.
Changes
- info
added the new optional
queryrequest parameterscope
- info