SavvyIQ API
Version 2026-08-05
The SavvyIQ API resolves business identity. Give it a name or a domain; get back a stable entity ID anchored to a government registration, plus the record we hold for that company.
How the endpoints fit together
Two entry points resolve an identity; one endpoint returns the record.
| You have | Call | You get |
|---|---|---|
| A company name | POST /v3/entity-resolution/async, then GET /v3/runs/{run_id} |
A siq_ entity ID |
| A domain | GET /v3/domain-intelligence |
A siq_ entity ID, plus what the domain is |
A siq_ entity ID |
GET /v3/entities/{id} |
The full record |
Resolve once, store the siq_ ID, and read the record from /v3/entities/{id} from then on.
IDs are stable.
From a resolved ID, ultimate parent research traces ownership upward under Entity hierarchy. Entity search and the MCP server for AI agents round out the surface.
One entity shape
The three record endpoints serve the same identity core: legal_name and display_name,
status, description, website, headquarters, typed identifiers[], and
primary_legal_entity, the government registration that anchors the record.
They differ only in how much they add on top. Entity resolution adds facets
(ownership and legal form) and scheme-keyed industry codes under industry.schemes.
/v3/entities/{id} adds those plus the enrichment: firmographics, classification labels,
operational footprint, social profiles. /v3/domain-intelligence serves the identity core
alone, next to everything it knows about the domain itself.
Base URL
https://api.savvyiq.ai