Backpack
Backpack is a Solana-first crypto company founded by Armani Ferrante and Tristan Yver — the same team behind Coral and the Anchor framework that powers a majority of Solana programs. It operates two flagship products: Backpack Wallet, an open-source self-custodial multichain wallet (Solana, Ethereum, Bitcoin) with an xNFT plugin runtime, available as a Chrome/Brave extension and iOS/Android app; and Backpack Exchange, a fully fledged centralized exchange offering spot, perpetual futures, dated futures, prediction markets, borrow/lend, RFQ, strategies, vaults, and securities, with a comprehensive ED25519-signed REST + WebSocket API documented at docs.backpack.exchange. Backpack Exchange acquired and processes FTX EU claims and is one of the more technically transparent venues to emerge post-FTX.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Backpack the way a machine reads it — 81 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Backpack scores 64.3/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Backpack
Each block below is one kind of artifact we hold for Backpack. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Backpack Wallet
Backpack Wallet is a self-custodial multichain wallet for Solana, Ethereum, and Bitcoin, originally built around the xNFT (executable NFT) protocol that lets dApps run as plugin...
Backpack Account API
Account settings and limits.
Backpack Assets API
Assets and collateral data.
Backpack Borrow Lend API
Borrowing and lending.
Backpack Borrow Lend Markets API
Borrowing and lending.
Backpack Capital API
Capital management.
Backpack Markets API
Public market data.
Backpack Order API
Order management.
Backpack Position API
Positions and futures data.
Backpack RFQ API
RFQ (Request For Quote) - Maker.
Backpack Strategy API
Strategies.
Backpack System API
Exchange system status.
Backpack Trades API
Public trade data.
Backpack Vaults API
Vault data.
Backpack Withdrawal Delays API
Withdrawal delays.
Scroll within the panel for all 15 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Backpack Exchange API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Backpack Exchange API
OPEN COLLECTIONArazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Backpack Balance-Checked Market Buy
Confirm available balance, read the ticker, then place a market buy and verify the fill.
ARAZZOBackpack Balance-Checked Withdrawal
Confirm available balance, request a withdrawal, then reconcile it against withdrawal history.
ARAZZOBackpack Cancel and Replace an Order
Look up a resting order, cancel it, and place a replacement at a new price.
ARAZZOBackpack Get Deposit Address and Reconcile History
Fetch a blockchain deposit address, then read deposit history to reconcile incoming funds.
ARAZZOBackpack Flatten Open Orders on a Market
List open orders on a market, cancel them all, and confirm none remain.
ARAZZOBackpack Market and Trade Analytics
Discover markets, pull all tickers, and read recent trades for a chosen symbol.
ARAZZOBackpack Place a Limit Order
Price a market from the ticker and order book, then place and confirm a limit order.
ARAZZOBackpack Add a Take-Profit to a Position
Read an open futures position and the mark price, then place a reduce-only take-profit order.
ARAZZOScroll within the panel for all 8 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Backpack Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Backpack Finops
FINOPSFeatures 19
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 19 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Backpack Exchange WebSocket Streams API
Real-time market data and account event streams for Backpack Exchange. Clients connect to a single WebSocket endpoint and manage many streams over that connection by sending `SU...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Backpack Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Backpack Balance
JSON SCHEMABackpack Market
JSON SCHEMABackpack Order
JSON SCHEMABackpack Position
JSON SCHEMABackpack Trade
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Backpack Depth Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Programmatic spot and perps trading
Build trading bots and execution algorithms against the Backpack Exchange order book using ED25519 signed requests and the orderExecute instruction set.
Real-time market data ingestion
Subscribe to WebSocket streams (ticker, depth, trades, klines, mark price, open interest, liquidation) for low-latency market state in research pipelines and dashboards.
Market making and RFQ liquidity provisioning
Respond to RFQs with quotes via /api/v1/rfq/quote and stream account.rfqUpdate events to compete on size-aware fills.
Lending and borrowing automation
Use the Borrow Lend endpoints to automate APY hunting across markets, manage liquidation price thresholds, and reconcile interest history.
Portfolio reconciliation and TaxOps
Pull fill, order, funding, settlement, deposit, and withdrawal history from /wapi/v1/history/* to build internal P&L and tax reporting.
Multichain wallet integration
Embed or extend the open-source Backpack wallet for Solana / Ethereum / Bitcoin signing flows, or ship dApps as xNFTs inside the wallet runtime.
Integrations 9
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Solana
Native settlement chain for the wallet and the home of the Anchor framework and xNFT protocol.
Ethereum
Supported in the multichain wallet for EVM signing and asset management.
Bitcoin
Supported in the multichain wallet for BTC custody and transfers.
TradingView
Charting integration exposed via the TradingView tag in the API for klines and ticker data.
Plaid
US fiat onramp identity verification used during KYC and bank-link flows.
Banxa
Third-party crypto onramp partner integrated into the deposit flow.
Easy Euro / Equals Money
EUR onramp partners surfaced as dedicated API tag groups in the exchange spec.
Sygna Bridge
Travel Rule compliance partner for cross-VASP withdrawal information sharing.
Coral / Anchor
Same founding team (Armani Ferrante) — Backpack ships on top of Anchor-based Solana programs.
Scroll within the panel for all 9 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Backpack Exchange
Centralized crypto exchange with spot, perpetuals, lending, RFQ, strategies, and prediction markets — accessible via the REST + WebSocket API.
Backpack Wallet
Self-custody multichain wallet with xNFT runtime, available as Chrome/Brave extension and iOS/Android apps.
Backpack EU
Regulated European entity surfaced via European Private Beta and FTX EU Claims tags.
FTX Creditor Claims processing
Dedicated tag group for processing FTX creditor and FTX EU claims through the exchange.
Resources
Every other property we hold for Backpack — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/backpack · machine-readable index on apis.io