Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FormulaSignal Intelligence 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%2Fformulasignal.com%2Fformulasignal" | 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%2Fformulasignal.com%2Fformulasignal" | 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 FormulaSignal Intelligence API.
Answer one bounded question from the covered pre-workout Record
Resolve a brand, product name, or alias to one canonical covered product
Return a product's current record and its classified historical timeline
Compare two or three covered products on consistent criteria
GET STARTED
Explain a reviewed change Signal between two comparable product states, with citations
Return ingredient dose ranges and documented regulatory cautions for named ingredients
Track a bound account's watchlist and read its monitoring receipt
Patterns agents use FormulaSignal Intelligence API for, with concrete tasks.
★ Agent Product Research
An AI agent connected through Jentic can resolve a pre-workout product by name, read its current record, and compare it against another product without a developer wiring the FormulaSignal API by hand. The agent searches by intent and receives bounded, citation-backed answers rather than raw data to re-interpret.
Resolve two pre-workout product names and compare them on consistent criteria, returning the differences
Change Monitoring
Analysts track when a product's declared formula or price changes. FormulaSignal returns approved Signals in release order for incremental polling and explains each confirmed change between two comparable product states, with the citation behind it.
Poll for new Signals since the last check and explain the most recent confirmed change
Ingredient and Regulatory Context
Researchers need the dose range used for an ingredient in the evidence set and the documented regulatory records for it. FormulaSignal returns research and regulatory context for named ingredients, each result carrying the class of record it actually is.
Return the dose range and regulatory cautions for a named ingredient with their citations
19 endpoints — the formulasignal intelligence api answers bounded questions about u.
METHOD
PATH
DESCRIPTION
/api/v1/record/search
Answer a bounded question from the Record
/api/v1/products/resolve
Resolve a name or alias to a canonical product
/api/v1/products/{product_id}
Get a product's current record
/api/v1/products/{product_id}/history
Get a product's historical timeline
/api/v1/products/compare
Compare two or three covered products
/api/v1/signals
List approved Signals, newest first
/api/v1/regulatory/context
Return regulatory context for named ingredients
/api/v1/record/search
Answer a bounded question from the Record
/api/v1/products/resolve
Resolve a name or alias to a canonical product
/api/v1/products/{product_id}
Get a product's current record
/api/v1/products/{product_id}/history
Get a product's historical timeline
/api/v1/products/compare
Compare two or three covered products
/api/v1/signals
List approved Signals, newest first
/api/v1/regulatory/context
Return regulatory context for named ingredients
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FormulaSignal Intelligence API by hand means handling its environment-prefixed bearer key, learning which route is public, and shaping each bounded question yourself. Through Jentic you install once, import FormulaSignal from the API Directory, store the key once, and your agent calls it.
Permission scoping
FormulaSignal exposes read and search operations alongside a small watchlist that can be modified, so a rule can let your agent resolve, read, and compare products while leaving the watchlist writes out. You choose the operations it may call, so changes like adding to or removing from the watchlist are not included unless you add them.
Credential isolation
Your FormulaSignal 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 'resolve a pre-workout product' or 'compare two products', and Jentic returns the matching FormulaSignal 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 FormulaSignal Intelligence API through Jentic.
What authentication does the FormulaSignal Intelligence API use?
The FormulaSignal Intelligence API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec; the key is environment-prefixed and an `X-FormulaSignal-Key` header is accepted as an alternative. The key is never read from a query string, so it cannot reach an access log. The health check is the only route that needs no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
Can I compare two pre-workout products with the FormulaSignal Intelligence API?
Yes. The compare operation evaluates two or three covered products on consistent FormulaSignal criteria in a single bounded call and returns the differences with the context behind them.
Can I limit what my agent is allowed to do with the FormulaSignal Intelligence API?
Yes. Write a rule that allows only the read and search operations, such as resolving products, reading records, and comparing them, so the agent cannot change the account watchlist. Every call it makes is logged.
Is there a FormulaSignal MCP server?
You do not need an MCP server to give your agent the FormulaSignal Intelligence API. Jentic connects it directly from the API Directory: import FormulaSignal, store your key once, and the agent calls its operations by intent without loading another server's tool definitions into its context.
What are the rate limits for the FormulaSignal Intelligence API?
The OpenAPI spec does not specify numeric rate limits for the FormulaSignal Intelligence API. Check the FormulaSignal documentation at https://formulasignal.com/developers/keys for current limits.
How do I look up a pre-workout product with the FormulaSignal Intelligence API through Jentic?
Search Jentic for an intent like 'resolve a pre-workout product', and it returns FormulaSignal's resolve and record operations with their input schemas so your agent can turn a product name into a canonical record. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Answer bounded questions about U.S. pre-workout supplement products: resolve a product, read its current record and history, compare products, and explain reviewed change Signals with citations. Retrieve ingredient dose ranges, regulatory cautions, and the published Category Ledger.
Use for: Search the Record for a specific question about a pre-workout product, Resolve a product name to its canonical product, Get the current record for a covered product, Retrieve the historical timeline for a product
Not supported: Does not export the full Record, list all products, or return source documents. Use for bounded, citation-backed answers about covered U.S. pre-workout products only.
The FormulaSignal Intelligence API answers bounded questions about U.S. pre-workout supplement products, drawing on a dated, evidence-backed Record of what products declare, what they cost per serving, and how those facts have changed. It resolves a brand or product name to a canonical product, returns a product's current record and classified historical timeline, compares products, and explains reviewed change Signals with their citations. Research and regulatory context endpoints return ingredient dose ranges and documented cautions, and a watchlist tracks monitoring state for a bound account.
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>