For Agents
Pull SEC filings, insider transactions, institutional holdings, and company profiles, and subscribe to new filings through webhooks.
Use for: List the most recent SEC filings, Get the details of a filing by its accession number, Show me the insider transactions for a company, Look up a company profile by its CIK
Not supported: Does not place trades, stream real-time prices, or file documents with the SEC. Use for reading SEC filings, insider and institutional data, and company profiles only.
The Earnings Feed API serves SEC filings, insider transactions, institutional holdings, and company data for public US companies. It lists filings and returns full detail by accession number, exposes insider transactions and institutional holdings, and resolves company profiles by CIK or through a company search. Webhook endpoints let you subscribe to new data and inspect their delivery history so a system can react as filings arrive rather than polling.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Earnings Feed 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%2Fearningsfeed.com%2Fearningsfeed" | shStep 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%2Fearningsfeed.com%2Fearningsfeed" | 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.
What an agent can do with Earnings Feed API.
List SEC filings and get full filing detail by accession number
List insider transactions and institutional holdings
Resolve a company profile by CIK or search companies by name
Create and list webhook endpoints that fire on new data
Inspect a webhook's delivery history
Patterns agents use Earnings Feed API for, with concrete tasks.
★ Agent-driven filings monitoring
An AI agent connected through Jentic lists new SEC filings, opens the ones that matter by accession number, and resolves the filer's company profile so an analyst gets a briefing on what was disclosed. The agent reads the filing and company data on demand and summarizes the material points.
List today's SEC filings, pull the detail for each 8-K, and summarize what was disclosed
Insider and institutional tracking
Research workflows track who is buying and selling by reading insider transactions and institutional holdings for the companies they follow. The API returns both datasets so an agent can report notable changes without parsing the underlying forms itself.
Pull the insider transactions and institutional holdings for a company and flag the largest recent moves
Webhook-driven ingestion
Instead of polling, teams create a webhook endpoint so Earnings Feed pushes new data as it arrives, then inspect the delivery history to confirm receipt. The API exposes create, list, delete, and delivery-history operations for webhooks, giving an agent a way to wire up and verify a feed.
Create a webhook endpoint for new filings and read its recent delivery history to confirm it is firing
11 endpoints — the earnings feed api serves sec filings, insider transactions, institutional holdings, and company data for public us companies.
METHOD
PATH
DESCRIPTION
/api/v1/filings
List SEC filings
/api/v1/filings/{accession}
Get filing details by accession number
/api/v1/insider/transactions
List insider transactions
/api/v1/institutional/holdings
List institutional holdings
/api/v1/companies/{cik}
Get a company profile by CIK
/api/v1/webhooks
Create a webhook endpoint
/api/v1/filings
List SEC filings
/api/v1/filings/{accession}
Get filing details by accession number
/api/v1/insider/transactions
List insider transactions
/api/v1/institutional/holdings
List institutional holdings
/api/v1/companies/{cik}
Get a company profile by CIK
/api/v1/webhooks
Create a webhook endpoint
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Earnings Feed by hand means handling its Bearer auth, resolving filings by accession number and companies by CIK, and standing up and verifying webhook endpoints yourself. Through Jentic you install once, import Earnings Feed from the API Directory, store the token once, and your agent calls it.
Permission scoping
Earnings Feed carries webhook ids, filing accession numbers, and company CIKs in the URL path, so a rule can pin your agent to the reads you pick, such as listing filings and reading company profiles. You choose the operations it may call, so webhook creation and deletion are not included unless you add them.
Credential isolation
Your Earnings Feed 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 'list SEC filings' or 'get insider transactions', and Jentic returns the matching Earnings Feed operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Earnings Feed API through Jentic.
What authentication does the Earnings Feed API use?
The Earnings Feed API authenticates with a Bearer token in the Authorization header per its OpenAPI spec; every endpoint requires it. Through Jentic the token is stored once and injected at call time so it never enters the agent's prompt.
Can I get SEC filing details with the Earnings Feed API?
Yes. You can list filings and fetch the full detail for one by its accession number, alongside insider transactions, institutional holdings, and company profiles resolved by CIK or company search.
What are the rate limits for the Earnings Feed API?
The spec documents tier-based per-minute and monthly limits that depend on your subscription. Check your Earnings Feed plan and documentation for the exact figures that apply to your key before running large backfills.
Is there an Earnings Feed API MCP server?
You don't need an MCP server to give your agent the Earnings Feed API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent reads filings and company data on demand without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Earnings Feed API?
Yes. Write a rule that allows only the filings-read and company-read operations, so the agent can pull filings and profiles but cannot create or delete webhook endpoints, and every call it makes is logged for review.
How do I monitor SEC filings with the Earnings Feed API through Jentic?
Search Jentic for 'list SEC filings', add the Earnings Feed API from the directory, and store your token once; your agent can then list new filings and pull their details on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED