Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Market 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%2Fmarketintelligenceapi.com%2Fmarketintelligenceapi" | 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%2Fmarketintelligenceapi.com%2Fmarketintelligenceapi" | 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 Market Intelligence API.
Read the live trade-flow signal for an asset such as ETHUSD over a 1m, 5m, or 15m window, including buy pressure and anomalies
Check an ERC-20 or Solana token for honeypot, admin, and holder risks, or get a short safe-to-buy verdict
Get a swap quote on the best on-chain route between a sell and a buy token
Pull SEC insider trades from Form 4, proposed sales from Form 144, 13D and 13G holders, and XBRL financial statements for a US company
GET STARTED
Read the US Treasury yield curve, ECB euro rates, net dollar liquidity, and Hyperliquid perp funding rates
Get a rule-based trading decision for a symbol and check the decisions' live hit rate on the free track record
Subscribe a webhook to alerts such as decision_change, unusual_flow, and stablecoin_depeg with a prepaid pack
Patterns agents use Market Intelligence API for, with concrete tasks.
★ Trading agent with a payment boundary through Jentic
A crypto research agent checks a token's risk, reads its trade flow, and asks for a decision before suggesting a trade. Through Jentic it calls the token-verdict, intelligence, and decision operations, with the x402 X-PAYMENT value injected at call time. A rule decides which paid routes the agent may call, which bounds what it can spend.
GET /api/v1/intelligence/token-verdict/{address} for address 0x940181a94a35a4569e4529a3cdfb74e38fd98631 with chain 'base', then GET /api/v1/intelligence/{symbol} for the token's symbol with window '5m', and summarise risk and buy pressure
Token due diligence before a swap
Before swapping into a newly launched token, a wallet assistant checks for honeypot behaviour, admin privileges, and holder concentration, looks at who bought and sold in the last hour, and fetches a swap quote. The chain query parameter names the chain the token lives on: base, ethereum, arbitrum, optimism, polygon, or solana.
GET /api/v1/intelligence/token-risk/{address} with chain 'ethereum', then GET /api/v1/intelligence/token-traders/{address} with limit 10, and only if no risk flags appear call GET /api/v1/intelligence/quote with the sell and buy tokens
Insider and ownership monitoring for US stocks
Equity analysts track insider activity from SEC filings. The API returns Form 4 insider trades, Form 144 proposed sales, 13D and 13G holders above five percent, dividends, and fails-to-deliver per ticker, with batch routes for insider trades and fundamentals on up to 10 tickers at once.
GET /api/v1/insiders/batch with symbols 'NVDA,AAPL,MSFT' and days 30, then GET /api/v1/sec/form-144/{symbol} for any ticker showing net insider selling
Rates and macro dashboard
Macro-aware agents read the US Treasury yield curve with slopes, SOFR, and euro STR, upcoming Treasury auctions, net dollar liquidity, US bank credit and deposits, ECB euro rates, and Eurostat inflation and unemployment by country. A macro calendar lists upcoming market-moving events by importance and region.
GET /api/v1/rates/curve and GET /api/v1/rates/liquidity, then GET /api/v1/calendar with days 7, and write a short note on the rates backdrop for the coming week
128 endpoints — the market intelligence api sells pay-per-call market signals built from observed data, paid with x402 micropayments in the x-payment header.
METHOD
PATH
DESCRIPTION
/api/v1/intelligence/{symbol}
Live trade-flow signal for one asset
/api/v1/intelligence/token-verdict/{address}
Safe-to-buy verdict for a token
/api/v1/intelligence/token-risk/{address}
Token honeypot, admin, and holder risk
/api/v1/intelligence/quote
Swap quote on the best route
/api/v1/decision/{symbol}
Trading decision for one symbol
/api/v1/insiders/{symbol}
Insider trades from SEC Form 4
/api/v1/rates/curve
Treasury yield curve, SOFR, and euro STR
/coverage
Data sources covering each symbol
/api/v1/intelligence/{symbol}
Live trade-flow signal for one asset
/api/v1/intelligence/token-verdict/{address}
Safe-to-buy verdict for a token
/api/v1/intelligence/token-risk/{address}
Token honeypot, admin, and holder risk
/api/v1/intelligence/quote
Swap quote on the best route
/api/v1/decision/{symbol}
Trading decision for one symbol
/api/v1/insiders/{symbol}
Insider trades from SEC Form 4
/api/v1/rates/curve
Treasury yield curve, SOFR, and euro STR
/coverage
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Market Intelligence API by hand means handling x402 payments: reading the 402 terms, signing a payment, and retrying with the X-PAYMENT header, while telling free routes from paid ones. Through Jentic you install once, import it from the API Directory, store your payment credential once, and your agent calls it.
Permission scoping
Symbols and token addresses sit in the URL path on many routes (/api/v1/intelligence/token-risk/{address}), so a rule can limit your agent to the operations you pick and, where it matters, one asset. You choose the operations it may call, so credit purchases and alert subscriptions are not included unless you add them.
Credential isolation
Your payment credential 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 'check if a token is safe to buy' or 'get the Treasury yield curve', and Jentic returns the matching operation with its input schema so the agent picks the right one of 128 routes without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Market Intelligence API through Jentic.
Is there a Market Intelligence API MCP server?
Yes - the spec itself includes MCP JSON-RPC routes at POST /mcp and POST /mcp/core. You can also connect the Market Intelligence API directly through Jentic: your agent gets the full 128-endpoint surface without loading another server's tool definitions into its context, your payment credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.
How does authentication and payment work on the Market Intelligence API?
Per its OpenAPI spec, paid routes use the x402 scheme: the payment travels in the X-PAYMENT header, and an unpaid call returns 402 with the payment terms. Free routes such as /coverage, /status, /api/v1/preview, and the decision track record need no auth. Prepaid credit keys are read with the X-API-Key header on the credits balance route, and alert subscription management uses an X-Alert-Secret header.
How much does a Market Intelligence API call cost?
The spec prices each paid call per route, in a range of $0.003-$0.05, and an unpaid request returns 402 with the exact price and payment terms. The discovery route /.well-known/x402-resources lists every paid resource, and routes such as /coverage and /status are free.
Can I limit what my agent is allowed to do with the Market Intelligence API?
Yes. Write a rule that allows only GET /api/v1/intelligence/token-verdict/{address}, GET /api/v1/intelligence/token-risk/{address}, and the free /coverage route, so a wallet assistant can vet tokens but cannot buy credit packs with POST /api/v1/credits/buy/{usd} or subscribe paid alerts. Your own instance runs those calls.
What are the rate limits for the Market Intelligence API?
The OpenAPI spec does not state a general rate limit. Usage is metered by payment per call; GET /status reports data freshness per chain and source, and GET /transparency describes the operator, data sources, and billing policy. See https://api.marketintelligenceapi.com/openapi.json for the current spec.
Which chains does the Market Intelligence API cover?
Trade flow comes from executed DEX trades on Base, Ethereum, Arbitrum, Optimism, Polygon, Robinhood Chain, and Solana. Token routes take a chain query parameter such as base, ethereum, arbitrum, optimism, polygon, or solana, which names where the token lives, not the payment network.
How do I check a token's risk through Jentic?
Add the Market Intelligence API to Jentic One from the directory and store your x402 payment credential once. Your agent searches for 'check if a token is safe to buy', calls GET /api/v1/intelligence/token-verdict/{address} with the contract address and chain, and reads the verdict. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Pay per call with x402 to get DEX trade-flow signals, token risk verdicts, swap quotes, SEC insider and fundamentals data, rates and macro data, and rule-based trading decisions for crypto and tokenized stocks.
Use for: Is this token safe to buy? Check 0x940181a94a35a4569e4529a3cdfb74e38fd98631 on Base, Get the current buy pressure for ETHUSD over the last 5 minutes, Which assets have unusually high trading activity right now?, Show insider buying and selling for NVDA from Form 4
Not supported: Does not execute trades, hold funds, or provide brokerage accounts. Use for pay-per-call market signals, token risk checks, filings, and rates data only.
The Market Intelligence API sells pay-per-call market signals built from observed data, paid with x402 micropayments in the X-PAYMENT header. Its core is on-chain order flow from executed DEX trades on Base, Ethereum, Arbitrum, Optimism, Polygon, Robinhood Chain, and Solana, covering buy and sell pressure, momentum, anomalies, smart-money wallets, candles, and daily datasets, alongside token risk checks and swap quotes. It also serves Hyperliquid perp funding and positioning, SEC EDGAR filings such as Form 4, Form 144, and 13D/13G, ECB, Eurostat, US Treasury, and Federal Reserve rates data, CFTC positioning, and rule-based trading decisions with a free public track record.
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.
Data sources covering each symbol
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>