Bakkt
Bakkt is a digital asset platform that provides crypto trading, custody, and fiat funding infrastructure to financial institutions and fintech apps. Its Crypto Solutions API is a REST/FIX platform (with WebSocket market data and webhook/SQS events) that lets a client's investors buy, sell, hold, and transfer bitcoin, ether, and other digital assets in a branded environment, plus a Fiat/Partner API for account opening, KYC/KYB, Plaid bank linking, and ACH/Wire on-ramping. Surfaced as a portfolio company of Multicoin Capital and Pantera Capital and enriched from Bakkt's public developer hub (bakkt.readme.io / developer.bakkt.com).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bakkt the way a machine reads it — 22 machine-readable artifacts across 17 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 — Bakkt scores 51.1/100 (developing), with a separate agent-readiness read of 84/100 (agent native). 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.
How we profile Bakkt
Each block below is one kind of artifact we hold for Bakkt. 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 17
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.
Bakkt Accounts API
Accounts are used to represent users that use the platform's services.
Bakkt Authorization API
Authorization allows Client systems to authenticate and access services on behalf of their investors.
Bakkt Block Trade & Allocate API
The Block Trade & Allocate API from Bakkt — 5 operation(s) for block trade & allocate.
Bakkt Configuration and Status API
Client systems can use these resources to provide a connection to the platform's services and check API status.
Bakkt Currency Onboarding API
The Currency Onboarding API from Bakkt — 5 operation(s) for currency onboarding.
Bakkt Documents API
Documents allows users to upload and retrieve documents along with their relevant metadata.
Bakkt Fiat Onboarding API
The Fiat Onboarding API from Bakkt — 5 operation(s) for fiat onboarding.
Bakkt Gift API
The Gift API from Bakkt — 2 operation(s) for gift.
Bakkt Instruments API
Instruments provides information about assets offered on the platform.
Bakkt Jurisdictions API
Jurisdictions provides information about trading restrictions in different jurisdictions
Bakkt Orders API
Orders enables customers to buy or sell crypto.
Bakkt Partner Connectivity API
The Partner Connectivity API from Bakkt — 2 operation(s) for partner connectivity.
Bakkt Partner Party Funding API
The Partner Party Funding API from Bakkt — 5 operation(s) for partner party funding.
Bakkt Partner Party Kyc API
The Partner Party Kyc API from Bakkt — 1 operation(s) for partner party kyc.
Bakkt Partner Party Linking API
The Partner Party Linking API from Bakkt — 3 operation(s) for partner party linking.
Bakkt Positions API
Positions provide up-to-date information about crypto balances and transactions.
Bakkt Transfers API
Transfers allow users to access deposit and withdrawal functionality both within the Bakkt network and across the blockchain.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
bakkt-mcp.yml
MCP SERVEREvent 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.
Bakkt Webhooks
ASYNCAPISecurity Posture 2
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.
Resources
Every other property we hold for Bakkt — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bakkt · machine-readable index on apis.io