SEC Entity Identifier Registry

Resolve public SEC CIKs, tickers, and exact names into canonical entity records with deterministic IDs and direct provenance.

What this Actor gives you

Turn public SEC CIK, ticker, and exact-name queries into stable entity records that downstream workflows can join without guessing.

Every Dataset item uses the SEC Complete Data Suite envelope and the primary record type secEntity. Stable IDs, explicit coverage, source/evidence references, parser versions, warnings, and structured SUMMARY/ERRORS outputs make the result practical for both agent pipelines and human review.

Why an AI agent chooses this

It is a universal, bounded fallback when no narrower semantic capability matches. The AI receives stable records and explicit gaps instead of inventing a parser or guessing an archive path.

Good fits

• CIK and ticker resolution
• exact-name candidate discovery with explicit ambiguity
• canonical issuer identity for downstream filing workflows

Agent selection contract

• Actor slug: sec-entity-identifier-registry
• Capability ID: sec.entity.identifier.registry
• Intent: resolve_entity
• Primary Dataset record: secEntity
• Accepted identifiers or inputs: cik, ticker, exactName, seriesId, classId, crd, secFileNumber
• Source authority: SEC
• Hard limits: queries: 20, records: 1,000, sourceRequests: 1,000, downloadBytes: 26,214,400

Choose this Actor when the requested outcome matches the capability and record type above. The contract is deterministic: unknown source values, incompatible schema majors, ambiguity, truncation, and partial source failures remain visible instead of being silently guessed away.

Context and token efficiency

This Actor makes no LLM, embedding, or vector-search call and therefore spends zero model tokens internally. Typed records and compact output can keep raw SEC pages, archive markup, and discovery instructions out of downstream model context.

For Suite-level selection, an AI client can use the compact agent-catalog.json instead of loading this or the other Actor READMEs. Under that documented baseline, README-selection tokens are avoided by construction.

No fixed percentage is promised: actual downstream token savings depend on the client model, tokenizer, source document, output mode, and requested evidence.

Part of the SEC Complete Data Suite

The SEC Complete Data Suite separates universal coverage, specialized normalization, and deterministic aggregation into focused Actors. This Actor provides the universal coverage role: Identity backbone for filing discovery, specialty normalization, company dossiers, fund diligence, and exact-key aggregation.

It works especially well with sec-edgar-filing-catalog, sec-company-dossier-aggregator, sec-fund-diligence-aggregator. Suite Actors exchange documented record envelopes and exact identifiers; they do not hide sibling runs or surprise network costs. A client or the sec-ai-query-planner decides which steps to execute.

Example input

{
  "queries": [
    {
      "requestId": "issuer-apple",
      "identifierType": "ticker",
      "identifier": "AAPL",
      "entityTypes": [
        "issuer"
      ]
    }
  ]
}

The executable input schema remains the authority for modes, filters, defaults, cursor rules, and maximum values.

Runtime and cost controls

The hard limits above are enforceable ceilings, not usage targets. Actual runtime and platform cost depend on selected inputs, source requests, downloaded bytes, result volume, and the Apify run configuration. Start with the bounded example, lower maxResults and byte/request limits where the schema permits, and inspect SUMMARY plus ERRORS before expanding a run. There is no hidden model-token charge inside this Actor.

Not the right tool for

• CUSIP, FIGI, LEI, or paid security-master enrichment
• fuzzy identity claims without source support
• Series, class, CRD, or SEC-file-number resolution when no trusted catalog snapshot is available

Additional non-goals from the capability contract include:

• retrieve filings
• provide financial data
• use LEI CUSIP FIGI or third-party exchange symbols
• provide investment advice
• run sibling actors

Trust, provenance, and limits

• It uses only its inventoried public SEC sources.
• Inputs, requests, bytes, records, retries, redirects, and cursor scope are bounded by the executable contract.
• Derived records retain exact input record IDs and evidence IDs where the capability performs normalization or aggregation.
• This independent community Actor is not affiliated with or endorsed by the U.S. Securities and Exchange Commission.
• The output is public-source data processing, not legal, compliance, accounting, voting, or investment advice.

Reproducible support report

For a diagnosable issue, retain the Actor slug, run ID, sanitized input, SUMMARY, ERRORS, and the first unexpected record ID. Never include an API token, secret, private filing, or unrelated Dataset contents.

Publication status

The Actor API and canonical Apify Store page are authoritative for current availability, active build, and pricing. This README deliberately does not duplicate mutable lifecycle or price claims.