EDGAR API

Name: EDGAR API
Brand: EDGAR API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer18 EndpointsREST

For Agents

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

Use for: I need to view filer account information, I want to generate ccc, Search for custom ccc, Find all request delegation invitations

Connect the EDGAR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EDGAR 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 EDGAR API.

View filer account information

Generate CCC

Create custom CCC

Request delegation invitations

Send delegation invitations

GET STARTED

Start building with EDGAR API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use EDGAR API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

18 endpoints — sec.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

EDGAR API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'view filer account information') and Jentic returns the matching EDGAR API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct EDGAR API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using EDGAR API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.