Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the boothcheck 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%2Fboothcheck.com%2Fboothcheck" | 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%2Fboothcheck.com%2Fboothcheck" | 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 boothcheck API.
Read what a stock's price implies for growth, duration, and margin
Search and discover companies across their SEC filings
Pull a company's financials and business revenue breakdown by ticker
Track insider trades, their 10b5-1 plan context, and 13F holders
Read a management guidance ledger and risk-factor additions
GET STARTED
Compare segment snapshots and peer cohorts for a company
Get a full narrative research report or its summary for a ticker
Patterns agents use boothcheck API for, with concrete tasks.
★ Read what's priced into a stock through Jentic
Let an agent read the implied expectations behind a share price instead of modelling them by hand. The agent passes a ticker and gets the growth, duration, and margin the current price assumes, derived from SEC filings. Through Jentic the priced-in operation is discovered by intent and called with its input schema, so the figure drops straight into a research note.
Read what is priced into a stock with GET /priced-in/{ticker}
Company financials lookup
Pull a company's fundamentals by ticker for a model or screen. The agent reads financials and the business revenue breakdown, all sourced from filings, so a research workflow can compare companies without scraping filings itself.
Pull a company's financials with GET /financials/{ticker}
Insider and holder monitoring
Watch who is buying, selling, and holding a stock. The agent reads insider trades with their 10b5-1 plan context and the 13F holder register for a ticker, so a monitoring workflow can flag notable activity sourced from filings.
List insider trades with GET /insider-activity/{ticker}, then read 13F holders with GET /holders/{ticker}
Filing search and reports
Find the right disclosure and read the derived analysis of it. The agent searches a company's filings and pulls the full narrative report for a ticker, so an analyst gets the relevant filing and its summary in one pass.
Search a company's filings with GET /filing-search/{ticker}, then read the full report with GET /report/{ticker}
41 endpoints — the boothcheck api serves read-only research data derived from sec filings, keyed by ticker.
METHOD
PATH
DESCRIPTION
/priced-in/{ticker}
What's priced into a stock
/financials/{ticker}
Company financials
/insider-activity/{ticker}
Insider trades with 10b5-1 context
/holders/{ticker}
13F holders register
/segments/{ticker}
Segment snapshot
/guidance-ledger/{ticker}
Management guidance ledger
/report/{ticker}
Full narrative report
/filing-search/{ticker}
Search a company filing
/priced-in/{ticker}
What's priced into a stock
/financials/{ticker}
Company financials
/insider-activity/{ticker}
Insider trades with 10b5-1 context
/holders/{ticker}
13F holders register
/segments/{ticker}
Segment snapshot
/guidance-ledger/{ticker}
Management guidance ledger
/report/{ticker}
Full narrative report
/filing-search/{ticker}
Search a company filing
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Boothcheck by hand means learning its bearer auth, which endpoints are public versus gated, and the ticker-keyed shape of every dataset. Through Jentic you install once, import Boothcheck from the API Directory, store the token once, and your agent calls it.
Permission scoping
Boothcheck puts the ticker in the URL path (/financials/{ticker}), and every operation is a read, so a rule can allow your agent just the datasets it needs, such as financials and holders, while leaving others out. You choose which operations it may call, so a research agent sees only the data you grant.
Credential isolation
Your Boothcheck 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 'what is priced into a stock' or 'get company financials', and Jentic returns the matching Boothcheck 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 boothcheck API through Jentic.
What authentication does the boothcheck API use?
The boothcheck API authenticates with a bearer token per its OpenAPI spec. Headline endpoints such as what's priced into a stock, the most-stretched list, and the coverage list are public, while filings, reports, financials, and insider data require the token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.
Can I read a company's financials and insider activity with the boothcheck API?
Yes. Pull a company's financials and business revenue breakdown by ticker, and read its insider trades alongside the 10b5-1 plan context and 13F holder register, all as read-only data derived from SEC filings.
Can I limit what my agent is allowed to do with the boothcheck API?
Yes. Every operation is a read, so a rule can allow your agent only the datasets it needs, such as financials and priced-in, while leaving insider or holder data out unless you add those operations. Boothcheck keys each dataset by ticker in the URL path, so access stays scoped to the reads you grant.
What are the rate limits for the boothcheck API?
The OpenAPI spec does not specify rate limits. Check the Boothcheck documentation at https://boothcheck.com for current limits before running broad screens.
Is there a boothcheck MCP server?
You don't need an MCP server to give your agent boothcheck. Jentic connects it directly from the API Directory: import it, store your token once, and your agent runs the priced-in, financials, and filing operations on demand. That also keeps extra tool definitions out of the agent's context.
How do I read what's priced into a stock with the boothcheck API through Jentic?
Search Jentic for 'what is priced into a stock' and it returns the boothcheck priced-in operation with its input schema. Your agent passes a ticker and reads back the implied growth, duration, and margin. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Read research data derived from SEC filings by ticker: what a stock price implies, financials and segment snapshots, insider and 13F holder registers, management guidance, and narrative reports across 41 endpoints. Informational use only, no ratings or price targets.
Use for: Get what is priced into a stock, Search a company's SEC filings, Pull a company's financials by ticker, List the insider trades for a ticker
Not supported: Does not place trades, give investment advice, or publish price targets or ratings. Use for reading derived research data from SEC filings only.
The boothcheck API serves read-only research data derived from SEC filings, keyed by ticker. It reports what a stock's price implies for growth, duration, and margin, searches and discovers companies across filings, and returns financials, segment snapshots, peer cohorts, and business revenue breakdowns. It also tracks a management guidance ledger, risk-factor additions, insider trades with their 10b5-1 plan context, dilution facts, share-count history, and 13F holders, with no house fair value, price target, or rating.
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>