Query it like data — or hand it to an agent
A REST API, and an MCP server.
Movements are objects. Pull them into a warehouse, or let an agent ask the question directly. The MCP window is open now — not in eighteen months.
MCP · lead with this
Connect the Census to your agent
One connection string. Your agent can then ask FirstSeen questions in natural language and get typed Movements back. Metered on queries, not seats — because agents burst.
- "Which of my accounts added a competitor’s ESP this quarter?"
- "List domains in fintech that hardened DMARC in the last 30 days."
- "Show new .io companies from August that already took payment."
# claude / cursor / any MCP client
{
"mcpServers": {
"firstseen": {
"url": "https://mcp.firstseen.io",
"headers": {
"Authorization": "Bearer $FS_TOKEN"
}
}
}
}REST · the same data, typed
Endpoints
| Method | Path | Returns |
|---|---|---|
| GET | /v1/census | Query the population with filters (tld, category, born-after). |
| GET | /v1/movements | Detected changes — the atomic unit. Filter by type, provider, date. |
| GET | /v1/trace/{domain} | Full dated history and current state for one domain. |
| POST | /v1/signals | Create a saved query; attach a webhook for real-time events. |
Auth
Bearer token per workspace. Scope tokens to Signals or to the full Census.
Rate limits
REST metered per token. MCP metered on queries, not seats — agents can burst without seat sprawl.
Status
Uptime and incidents on the public status page.
Build on the date nobody else has.
API + MCP are on the Intelligence plan. Tell us the agent workflow you have in mind.