canonical: https://jentic.com/apis/arbitron.app/arbitron # Arbitron App Arbitron API 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. ## For AI 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. ## Scope Does not place trades, move funds, or connect exchange accounts. Use for reading perpetual-futures funding rates, spreads, and account analytics only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'current funding rates', load the operation schema, and execute with Jentic-injected credentials ## Key endpoints | 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 | ## Key resources - **Funding** — Current funding per venue and symbol, one coin's funding across venues, and funding history - **Spreads** — Current cross-venue spreads and backtested spreads - **Reference data** — The tracked venues, coins with a funding page, and the listings calendar - **Account** — Connected-account cards, trades, PnL, balances, positions, and key usage ## AI readiness 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. - **Score:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 53 / 100 - AI-Readiness & Agent Experience: 60 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 94 / 100 - **View full report:** https://jentic.com/apis/arbitron.app/arbitron/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **CoinGecko** — Broad crypto market data, versus Arbitron's focus on perpetual-futures funding and spreads. - **CoinMarketCap** — Market-cap and price context to pair with Arbitron's funding and spread data. ## FAQ ### 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.