Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Financial Datasets 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%2Ffinancialdatasets.ai%2Ffinancial-datasets" | 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%2Ffinancialdatasets.ai%2Ffinancial-datasets" | 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 Financial Datasets API.
Retrieve historical and real-time stock and crypto prices
Pull income statements, balance sheets, and cash flow statements
Get financial metrics, earnings snapshots, and analyst estimates
Read insider trades and institutional ownership holdings
Fetch SEC filings, filing items, and company facts
GET STARTED
Read macro series such as central-bank interest rates
Screen financial statements and search specific line items
Patterns agents use Financial Datasets API for, with concrete tasks.
★ Agent Financial Research via Jentic
AI agents gather market data through Jentic without holding the API key in context. An agent searches by intent, receives the matching operation schema, and pulls prices, statements, or filings for a research task end to end. Jentic injects the key at execution time, so the agent never sees the secret while it assembles the data it needs.
Search Jentic for 'get a stock price from Financial Datasets', load the GET /prices schema, and fetch prices with Jentic-managed credentials
Automated Fundamental Analysis
An agent builds a fundamental picture of a company by pulling its income statements, balance sheets, and cash flow statements, then layering on financial metrics and analyst estimates. Because the API returns structured statements across many years, the agent can compute trends and ratios without scraping filings by hand.
Call GET /financials/income-statements and GET /financials/balance-sheets to assemble the fundamentals for a ticker
Filing and Insider Monitoring
An agent watches a set of companies by pulling their latest SEC filings and recent insider trades on a schedule, flagging anything notable. The API exposes filings and insider-trade endpoints directly, so the agent can surface disclosures without polling the SEC website itself.
Call GET /filings and GET /insider-trades for each watched company and flag new disclosures
37 endpoints — the financial datasets api gives ai agents structured stock market data covering thousands of tickers over decades.
METHOD
PATH
DESCRIPTION
/prices
Get historical stock price data
/financials/income-statements
Get income statements
/financials/balance-sheets
Get balance sheets
/insider-trades
Get insider trades
/filings
Get SEC filings
/news
Get news articles
/earnings
Get an earnings snapshot
/prices
Get historical stock price data
/financials/income-statements
Get income statements
/financials/balance-sheets
Get balance sheets
/insider-trades
Get insider trades
/filings
Get SEC filings
/news
Get news articles
/earnings
Get an earnings snapshot
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Financial Datasets API by hand means setting the X-API-KEY header, choosing among dozens of price, statement, and filing endpoints, and paging results yourself. Through Jentic you install once, import the Financial Datasets API from the API Directory, store the key, and your agent calls it.
Permission scoping
This API is read-only, and you choose which operations your agent may call, so a rule can allow price and financial-statement lookups while withholding insider-trade or ownership data. Scoping is by operation, so the agent reaches only the endpoints you approve.
Credential isolation
Your Financial Datasets 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 a stock price' or 'pull an income statement', and Jentic returns the matching Financial Datasets 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 Financial Datasets API through Jentic.
What authentication does the Financial Datasets API use?
The Financial Datasets API authenticates its data operations with an API key sent in the `X-API-KEY` header, per its OpenAPI spec. A set of public reference endpoints that list available tickers, CIKs, and filing types need no key. 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 financial statements with the Financial Datasets API?
Yes. Retrieve income statements with GET /financials/income-statements, balance sheets with GET /financials/balance-sheets, and historical prices with GET /prices.
What are the rate limits for the Financial Datasets API?
The OpenAPI spec does not specify rate limits; check the Financial Datasets documentation for current limits. Through Jentic, requests run from your own instance, so you control the pacing of the agent's calls.
How do I get a stock price with the Financial Datasets API through Jentic?
Search Jentic for 'get a stock price from Financial Datasets', load the returned GET /prices operation with its input schema, and your agent fetches the data with credentials injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Financial Datasets MCP server?
You don't need an MCP server to give your agent the Financial Datasets API. Jentic connects it directly from the API Directory: import it, store your key, and your agent calls it, discovering operations on demand instead of loading a separate server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Financial Datasets API?
Yes. This API is read-only, and you choose which operations your agent may call, so you can grant price and filing lookups while withholding insider-trade or institutional-ownership data. The agent invokes only the endpoints on your allow list and nothing more.
For Agents
Pull prices, financial statements, filings, insider trades, and macro data for public companies. Data operations authenticate with an X-API-KEY header.
Use for: I want the latest stock price for a ticker, Pull the income statement for a company, Check recent insider trades for a stock, Find the most recent SEC filings for a company
Not supported: Does not place trades or manage a portfolio. Use for market, fundamental, and filing data retrieval only.
The Financial Datasets API gives AI agents structured stock market data covering thousands of tickers over decades. Agents pull historical and real-time equity and crypto prices, income statements, balance sheets, and cash flow statements, plus financial metrics, earnings, and analyst estimates. They also read insider trades, institutional ownership, SEC filings, company facts, and macro series such as central-bank interest rates. A set of public reference endpoints lists the available tickers, CIKs, and filing types, while the data operations authenticate with an X-API-KEY header.
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>