canonical: https://jentic.com/apis/sec.gov/sec-gov

# Sec Gov EDGAR API

sec.gov/main version 1.11.0. The API exposes 18 endpoints secured with bearer authentication.

## For AI agents

Programmatically view filer account information, generate ccc. Covers 18 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- View filer account information
- Generate CCC
- Create custom CCC
- Request delegation invitations
- Send delegation invitations
- Add individuals

## Use cases

### Developer Tools Operations

Use the EDGAR API to perform developer tools operations programmatically. The API provides 18 endpoints covering core functionality including view filer account information, generate ccc, create custom ccc.

Example prompt: Call GET `/fm/{cik}` to view filer account information

### Automated EDGAR Operational Status API Management

Automate edgar operational status API operations by combining multiple EDGAR API endpoints. Agents can generate ccc and then create custom ccc in a single workflow.

Example prompt: Call POST `/fm/{cik}/ccc` to generate ccc, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call EDGAR 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 bearer tokens manually.

Example prompt: Search Jentic for 'view filer account information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/fm/{cik}` | View filer account information |
| POST | `/fm/{cik}/ccc` | Generate CCC |
| PUT | `/fm/{cik}/ccc` | Create custom CCC |
| POST | `/fm/{cik}/delegationRequests` | Request delegation invitations |
| POST | `/fm/{cik}/delegations` | Send delegation invitations |
| GET | `/fm/{cik}/delegations` | View delegations |
| POST | `/fm/{cik}/individuals` | Add individuals |
| GET | `/fm/{cik}/individuals` | View individuals |

## Key resources

- **EDGAR Operational Status API** — This API reports the status of the EDGAR system. This resource requires presentation of a Filer API
- **Filer Management API** — A set of API endpoints that allows you to verify permissions, get filer information, manage CCC,
- **Submission API** — Submission of filings to EDGAR by API can be made through the Submission API. The Submission API
- **Submission Status API** — The Submission Status API provides information from the EDGAR system. It requires a Filer API To

## Why Jentic

- **Setup:** Wiring the EDGAR API by hand means obtaining its filer and user bearer tokens, working through its filer-management request shapes, and managing delegations and CCC calls yourself. Through Jentic you install once, import EDGAR from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** EDGAR puts the filer CIK in the URL path (`/fm/{cik}/...`), so a rule can pin your agent to one filer: it can read that filer's account and individuals and nothing else. You choose the operations it may call, so writes like rotating the CCC or creating delegation requests are not included unless you add them.
- **Credential handling:** Your EDGAR token 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.
- **Discovery method:** Agents search Jentic by intent such as 'view filer account information' or 'list a filer's delegations', and Jentic returns the matching EDGAR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the EDGAR API use?

The EDGAR API uses a Bearer token 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 view filer account information with the EDGAR API?

Yes. Use the GET `/fm/{cik}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the EDGAR 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 view filer account information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'view filer account information'. Jentic returns the matching EDGAR API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the EDGAR API have?

The EDGAR API exposes 18 endpoints covering edgar operational status API, filer management API, submission API operations.

### Can I limit what my agent is allowed to do with the EDGAR API?

Yes. Because you run Jentic One yourself, your own rules decide which EDGAR operations and credentials the agent may use, and since EDGAR puts the filer CIK in the URL path (`/fm/{cik}/...`) a rule can pin the agent to a single filer. You can allow read-only calls like GET `/fm/{cik}` to view account information and GET `/fm/{cik}/individuals` while leaving out write operations such as POST `/fm/{cik}/ccc` to rotate the CCC or POST `/fm/{cik}/delegationRequests.` The agent can only call the operations you explicitly grant, and its bearer token is injected at execution time rather than exposed to the model.