SEC-API Mapping API
Official vendor OpenAPI document · agent-readyMaps GeolocationMappingapiKey13 EndpointsREST
For Agents
Programmatically map cik to company details, map ticker to company details. Covers 13 operations with apiKey authentication.
Use for: I need to map cik to company details, I want to map ticker to company details, Search for map cusip to company details, Find all map company name to company details
Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.
EDGAR mapping API for looking up SEC filings data by CIK, ticker, CUSIP, company name, exchange, sector, and industry. The API exposes 13 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the SEC-API Mapping API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SEC-API Mapping API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsec-api.io%2Fsec-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsec-api.io%2Fsec-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SEC-API Mapping API.
Map CIK to company details
List all companies on a given exchange
Integrate SEC-API Mapping API into automated workflows
Query and filter SEC-API Mapping API records by parameters
Monitor SEC-API Mapping API operational status and events
Use Cases
Patterns agents use SEC-API Mapping API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the SEC-API Mapping API to perform maps geolocation operations programmatically. The API provides 13 endpoints covering core functionality including map cik to company details, map ticker to company details, map cusip to company details.
Call GET /mapping/cik/{cik} to map cik to company details
Automated Bulk Downloads Management
Automate bulk downloads operations by combining multiple SEC-API Mapping API endpoints. Agents can map ticker to company details and then map cusip to company details in a single workflow.
Call GET /mapping/ticker/{ticker} to map ticker to company details, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SEC-API Mapping API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'map cik to company details', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — edgar mapping api for looking up sec filings data by cik, ticker, cusip, company name, exchange, sector, and industry.
METHOD
PATH
DESCRIPTION
GET
/mapping/cik/{cik}
Map CIK to company details
GET
/mapping/ticker/{ticker}
Map ticker to company details
GET
/mapping/cusip/{cusip}
Map CUSIP to company details
GET
/mapping/name/{name}
Map company name to company details
GET
/mapping/exchange/{exchange}
List all companies on a given exchange
GET
/mapping/sector/{sector}
List all companies in a given sector
GET
/mapping/industry/{industry}
List all companies in a given industry
GET
/bulk/mapping/cik-to-ticker
Download all CIK-to-ticker mappings
GET
/mapping/cik/{cik}
Map CIK to company details
GET
/mapping/ticker/{ticker}
Map ticker to company details
GET
/mapping/cusip/{cusip}
Map CUSIP to company details
GET
/mapping/name/{name}
Map company name to company details
GET
/mapping/exchange/{exchange}
List all companies on a given exchange
GET
/mapping/sector/{sector}
List all companies in a given sector
GET
/mapping/industry/{industry}
List all companies in a given industry
GET
/bulk/mapping/cik-to-ticker
Download all CIK-to-ticker mappings
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SEC-API Mapping API by hand means deciding whether to send its key in the Authorization header or the token query parameter, then building each CIK, ticker, and CUSIP lookup yourself. Through Jentic you install once, import SEC-API Mapping from the API Directory, store the key once, and your agent calls it.
Permission scoping
The SEC-API Mapping API is read-only, resolving identifiers through path lookups like /mapping/cik/{cik} and /mapping/ticker/{ticker}, so scope by operation: limit the agent to the lookups it needs, such as mapping a CIK or a ticker, none of which change any data.
Credential isolation
Your SEC-API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'map a CIK to company details' or 'find a company by ticker', and Jentic returns the matching SEC-API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SEC-API Mapping API through Jentic.
What authentication does the SEC-API Mapping API use?
The SEC-API Mapping API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I map cik to company details with the SEC-API Mapping API?
Yes. Use the GET /mapping/cik/{cik} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SEC-API Mapping API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I map cik to company details through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'map cik to company details'. Jentic returns the matching SEC-API Mapping API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SEC-API Mapping API have?
The SEC-API Mapping API exposes 13 endpoints covering bulk downloads, mapping operations.
Can I limit what my agent is allowed to do with the SEC-API Mapping API?
Yes. Because Jentic One is self-hosted, the operator's own rules decide which SEC-API Mapping operations and credentials the agent may use. The SEC-API Mapping API is read-only, so you can scope the agent to just the lookups it needs, for example allowing GET /mapping/cik/{cik} and GET /mapping/ticker/{ticker} while withholding the exchange, sector, or industry listings. None of these operations change any data, so a scoped agent can only resolve the identifiers you permit.
GET STARTED