Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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.gov%2Fsec-gov" | sh

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.gov%2Fsec-gov" | 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 One

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

/fm/{cik}/delegations

View delegations

POST

/fm/{cik}/individuals

Add individuals

GET

/fm/{cik}/individuals

View individuals

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

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

Sec Gov EDGAR API

Name: EDGAR API
Brand: EDGAR API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper 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

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

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

Jentic One on Github View OpenAPI Document

Connect the EDGAR API to your agent

Capabilities

Start building with EDGAR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sec Gov EDGAR API