For Agents
Retrieve normalized US-GAAP financial statements and SEC filing metadata for public companies, search companies, and compare as-reported figures against restatements.
Use for: Get the latest GAAP income statement for a public company, Fetch financial statements for a batch of tickers, Search for a company by its ticker symbol, List the most recent SEC filings
Not supported: Does not handle trading, real-time market prices, or portfolio management. Use for retrieving SEC-sourced financial statements and filings only.
The Datavidence Financials API returns normalized US-GAAP financial statements and SEC submission metadata sourced from SEC EDGAR XBRL filings. It searches companies, lists recent filings, and retrieves financial statements for one company or a batch of companies in a single request. It also exposes revisions that compare as-reported figures against later restatements, and a usage endpoint for checking consumption.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Datavidence Financials 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%2Fdatavidence.ai%2Fdatavidence" | 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%2Fdatavidence.ai%2Fdatavidence" | 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 Datavidence Financials API.
Retrieve normalized US-GAAP financial statements for a public company
Fetch financial statements for many companies in a single batch request
Search companies by name or ticker
List recent SEC filings and submission metadata
Compare as-reported figures against later restatements with the revisions data
Check your current API usage
Patterns agents use Datavidence Financials API for, with concrete tasks.
★ Agent-Driven Financial Statement Retrieval
An AI agent performing fundamental analysis can pull a company's normalized US-GAAP income statement, balance sheet, and cash flow from the Datavidence Financials API, which sources them from SEC EDGAR XBRL filings. Because the figures are already normalized, the agent can compare companies without reconciling differing filing formats.
Fetch the GAAP financial statements for a given ticker and most recent fiscal year, then summarize revenue and net income
Multi-Company Batch Screening
Research tools can request financial statements for many companies at once to screen a universe of tickers. The Datavidence Financials API returns normalized GAAP figures per company in a single batch call, so a screen does not need one request per company.
Request financial statements for a batch of tickers and rank them by net margin
Restatement and Filing Monitoring
Compliance and audit workflows can track when reported figures are later restated and when new filings land. The Datavidence Financials API lists recent SEC submissions and exposes revisions that pair as-reported values with their restated versions, so a monitor can flag the exact line items that changed.
List recent SEC filings for a company and flag any line items that were restated
6 endpoints — the datavidence financials api returns normalized us-gaap financial statements and sec submission metadata sourced from sec edgar xbrl filings.
METHOD
PATH
DESCRIPTION
/v1/extract-ledger
Get financial statements
/v1/extract-ledger/batch
Get financial statements for many companies
/v1/submissions
List recent SEC filings
/v1/companies
Search companies
/v1/revisions
Get revisions, as reported versus restated
/v1/usage
Check your usage
/v1/extract-ledger
Get financial statements
/v1/extract-ledger/batch
Get financial statements for many companies
/v1/submissions
List recent SEC filings
/v1/companies
Search companies
/v1/revisions
Get revisions, as reported versus restated
/v1/usage
Check your usage
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 the Datavidence Financials API by hand means managing its X-API-Key header, choosing between the direct host and the RapidAPI gateway, and parsing its normalized GAAP response envelope yourself. Through Jentic you install once, import the API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Datavidence Financials API takes the company and year as query parameters rather than in the URL path, so rules bound which operations your agent may call rather than which company. Limit it to the read operations it needs, such as fetching financial statements and searching companies, and leave out anything you did not include.
Credential isolation
Your Datavidence 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 'get GAAP financial statements' or 'list recent SEC filings', and Jentic returns the matching Datavidence operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Datavidence Financials API through Jentic.
What authentication does the Datavidence Financials API use?
The Datavidence Financials API authenticates with an API key sent in the `X-API-Key` header, per its OpenAPI spec. A sandbox demo key returns fixed sample data, and live access is keyed per subscriber. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I get GAAP financial statements with the Datavidence Financials API?
Yes. The extract-ledger operation returns normalized US-GAAP financial statements for a company and fiscal year, and a batch variant returns them for many companies in one request. You can also search companies and list their recent SEC filings to find the right identifier first.
What are the rate limits for the Datavidence Financials API?
The OpenAPI spec does not publish specific rate limits. Live plans are metered per subscription, and you can check your current consumption with the usage operation; see the provider's pricing page at https://financials.datavidence.ai/pricing for the limits that apply to your plan.
Can I limit what my agent is allowed to do with the Datavidence Financials API?
Yes. Every operation is a read, and the company and year travel as query parameters rather than in the URL path, so a rule bounds which operations the agent may call. Write a rule that allows only the statement-retrieval and company-search operations, so the agent can read financials and look up tickers and nothing else, and every call it makes is logged.
How do I retrieve a company's financials with the Datavidence Financials API through Jentic?
Search Jentic for 'get GAAP financial statements for a company' and it returns the extract-ledger operation with its input schema. Import the Datavidence Financials API from the Jentic API Directory, store your API key once, and your agent can fetch statements, run batch pulls, and list filings. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Where does the Datavidence Financials API get its data?
The data is sourced from SEC EDGAR XBRL filings and normalized into a consistent US-GAAP structure. Submission metadata and the revisions comparison come from the same filings, so you can trace a figure back to the filing it was reported in.
GET STARTED