Resolve a known identifier or company name
/v1/entities/resolve accepts ticker or symbol, CIK, FIGI-family identifiers, ISIN, CUSIP, or name/query/q. A successful response identifies the entity and can include its canonical CIK, primary identifiers, matchBasis, and matchConfidence. Preserve those match fields and requestId; use the CIK when a later SEC workflow needs a durable issuer key.
For discovery rather than a best-match lookup:
GET /v1/entities searches canonical issuers, managers, insiders, and funds with q, entity_type, limit, and cursor. The EDGAR-specific list surface is GET /v1/entities/edgar.
Move from identity to the requested data
/v1/companies/overview accepts a ticker, symbol, or CIK. Its optional REST enrichments such as segments, footnotes, dilution, and factors can degrade independently; retain the base result and expose the enrichment state instead of treating a partial response as a complete briefing.
SDK and MCP paths
The JavaScript SDK exposesclient.resolveEntity, client.companyOverview, client.companyFinancials, and client.companySearch. Hosted MCP offers entities.resolve, companies.overview, and companies.financials; the latter accepts one issuer or a supported ticker batch and returns per-entity status. Use REST or the SDK for the full canonical entity search and its cursor controls.
Identity and coverage caveats
- A high-confidence match does not settle corporate actions, reporting perimeter, historical ticker changes, or a security-to-issuer relationship in every use case.
- Do not use name search alone as authorization to silently substitute an issuer. Present the match basis when an ambiguous name feeds an investor-facing result.
- Company financial data remains filing-backed and period-specific. Follow its accession number and filing URL when it supports a material decision.
- A failed lookup is not a negative claim about a company; retain the request ID and correct the identifier or query.

