Arbitron App Arbitron API
68
AI ReadinessAI-Aware (B+)68/100
Official vendor OpenAPI document · agent-readyFinanceBankingbearer20 EndpointsREST
For Agents
Read perpetual-futures funding rates, cross-venue spreads, listings, and a connected account's trades and PnL, across 20 read-only endpoints secured with an API key.
Use for: Get the current funding rate for every venue and symbol, I need to compare cross-venue spreads for a coin, Find all announced listings and delistings, Retrieve my PnL calendar
Not supported: Does not place trades, move funds, or connect exchange accounts. Use for reading perpetual-futures funding rates, spreads, and account analytics only.
The Arbitron API serves funding rates, cross-venue spreads, and the listings calendar across the perpetual futures venues it tracks. It returns the current funding rate for every venue and symbol, one coin's funding across venues, current and backtested spreads, and announced listings and delistings, all as read-only JSON over HTTPS. For a connected account it also reads trades, the PnL calendar, balances and open positions, and the API key's own usage and limits. Everything is read-only: the API reports market and account data but does not place trades or move funds.
Install Jentic One Beta
Connect the Arbitron API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Arbitron 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.
1
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%2Farbitron.app%2Farbitron" | sh2
Step 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%2Farbitron.app%2Farbitron" | 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.
Capabilities
What an agent can do with Arbitron API.
Read the current funding rate for every venue and symbol, or one coin's funding across venues
Compare current cross-venue spreads and backtest historical spreads between perpetual futures venues
Track announced listings and delistings across the venues Arbitron covers
Pull a connected account's trades, PnL calendar, balances, and open positions
Check an API key's usage and remaining limits
Use Cases
Patterns agents use Arbitron API for, with concrete tasks.
★ Funding and Spread Monitoring
Watch where perpetual-futures funding and cross-venue spreads move. An agent reads the current funding rate for every venue and symbol, drills into one coin across venues, and compares live spreads against a backtest to spot persistent gaps. The data is read-only JSON, so the agent reports opportunities without ever placing a trade.
Read current funding across venues, then compare live spreads with the backtest for one coin
Account and PnL Review
Summarise a connected trading account on demand. The agent reads the PnL calendar, balances, open positions, and trade history for the account tied to the API key, then reports performance over a chosen window. Because the API is read-only, the agent can review the account but cannot change it.
Fetch the PnL calendar and balances for the connected account and summarise the last 30 days
AI Agent Integration via Jentic
An AI agent discovers and calls Arbitron through Jentic without handling the API key directly. The agent searches by intent, receives the matching read operation and its input schema, and executes the call while Jentic injects the stored key. This gives the agent live funding and spread data without reading the reference docs or holding secrets.
Search Jentic for 'current funding rates', load the operation schema, and execute with Jentic-injected credentials
Key Endpoints
20 endpoints — the arbitron api serves funding rates, cross-venue spreads, and the listings calendar across the perpetual futures venues it tracks.
METHOD
PATH
DESCRIPTION
GET
/api/v1/funding
Current funding rate on every venue and symbol
GET
/api/v1/funding/{coin}
One coin's funding across venues
GET
/api/v1/spreads
Current cross-venue spreads
GET
/api/v1/spreads/backtest
Backtested cross-venue spreads
GET
/api/v1/listings
Announced listings and delistings
GET
/api/v1/me/pnl
Your PnL calendar
GET
/api/v1/funding
Current funding rate on every venue and symbol
GET
/api/v1/funding/{coin}
One coin's funding across venues
GET
/api/v1/spreads
Current cross-venue spreads
GET
/api/v1/spreads/backtest
Backtested cross-venue spreads
GET
/api/v1/listings
Announced listings and delistings
GET
/api/v1/me/pnl
Your PnL calendar
Jentic AI Readiness Score
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.
A
Arbitron API
- AI-Aware (B+)68/100
74
Foundational Compliance53
Developer Experience & Jentic Compatibility60
AI-Readiness & Agent Experience94
Agent Usability60
Security94
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
53
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
5%
Example Density
How richly the API is illustrated with examples.
63%
Example Validity
Percentage of examples that conform to their schemas.
44%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
60
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
20%
Description Coverage
Coverage of descriptions across API elements.
75%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
95%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
49%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
94
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
94%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Arbitron by hand means creating a key, sending it as arb_live_ in the Authorization header on arbitron.app, and tracking its minute and month windows yourself. Through Jentic you install once, import Arbitron from the API Directory, store the key once, and your agent calls it.
Permission scoping
Arbitron is read-only, so through Jentic you limit the agent to the read operations it needs, such as funding rates and spreads, while leaving the private account operations like trades, PnL, and balances out of the set.
Credential isolation
Your Arbitron 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 'current funding rates' or 'cross-venue spreads', and Jentic returns the matching Arbitron operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Arbitron API through Jentic.
What authentication does the Arbitron API use?
The Arbitron API authenticates with an API key sent as a Bearer token in the Authorization header, per its OpenAPI spec; the X-Api-Key header is accepted as well. Keys look like arb_live_ followed by random characters and are created in your Arbitron settings. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so the agent never sees it.
Is there an Arbitron MCP server?
You do not need a separate MCP server to give your agent Arbitron. Jentic connects it directly from the API Directory: import Arbitron, store your key once, and your agent calls its funding and spread operations on demand. Operations are discovered as needed, so no extra server's tool definitions load into the agent's context.
Can I read cross-venue spreads with the Arbitron API?
Yes. Call the current spreads operation for live cross-venue spreads, or the backtest operation to see how a spread behaved historically. Both return read-only JSON that an agent can rank and act on, and neither places a trade.
Can I limit what my agent is allowed to do with the Arbitron API?
Yes. Arbitron is read-only, and because you run Jentic One yourself your rules decide which of its operations the agent may call. You can allow public market data such as funding rates and spreads while withholding the private account operations like trades, PnL, and balances, and every call is logged.
What are the rate limits for the Arbitron API?
Each key carries a per-minute window and a per-month window, but the OpenAPI spec does not pin exact numbers; the live values come back on the usage operation and in your account. See the Arbitron developer documentation at https://arbitron.app/developers for current limits.
How do I read funding rates with the Arbitron API through Jentic?
Search Jentic for 'current funding rates' to get the matching Arbitron operation and its input schema, then your agent calls it and parses the returned JSON per venue and symbol. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED