Bolt
Bolt is a checkout experience platform that provides a REST API for one-click checkout, managing shopper accounts, processing payments, and accessing shopper network data across merchants. Bolt enables mid-market and enterprise eCommerce merchants to integrate optimized, frictionless checkout across platforms including Adobe Commerce, BigCommerce, Shopify, WooCommerce, and Salesforce Commerce Cloud. The Bolt Shopper Network allows returning shoppers to complete purchases with stored credentials across all Bolt-powered merchants.
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 Bolt the way a machine reads it — 110 machine-readable artifacts across 13 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 — Bolt scores 56.7/100 (developing), with a separate agent-readiness read of 48/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 Bolt
Each block below is one kind of artifact we hold for Bolt. 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 13
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.
Bolt API
Core Bolt REST API for generating order tokens, managing transactions, pulling financial statements, and integrating one-click checkout into merchant storefronts. Supports both ...
Embeddable Checkout v3 API
API for configuring and embedding Bolt's checkout experience and shopper account management directly into merchant storefronts, including login modals, account creation, passwor...
Merchant Callback API
API enabling merchant backends to respond to Bolt checkout events including discount application, cart creation and updates, shipping and tax calculations, and transaction statu...
Subscriptions API
API for creating and managing Bolt Subscriptions, enabling recurring billing and subscription commerce on top of the Bolt checkout platform.
Tokenizer API
API for implementing custom back-office integrations including direct payment processing and card tokenization for merchant-side payment workflows.
Bolt Connect Merchant Onboarding API
API for platforms to complete connected merchant onboarding to Bolt, enabling platform partners to programmatically onboard new merchants.
Checkout Everywhere API
Beta API enabling Bolt checkout links and checkout experiences across any surface, including social commerce, email, and other off-site channels.
Bolt Account API
Use the Accounts API to access shoppers' accounts to empower your checkout and facilitate shoppers' choices.
Bolt Callbacks API
Implement Callback endpoints on your servers to power Bolt experiences. Different Bolt packages require different callbacks to be implemented. Consult your relevant product docu...
Bolt OAuth API
Use the OAuth API to enable your ecommerce server to make API calls on behalf of a Bolt logged-in shopper.
Bolt Orders API
Use the Orders API to create and manage orders, including orders that have been placed outside the Bolt ecosystem.
Bolt Payments API
Use the Payments API to process credit card and alternative payment methods with Bolt.
Bolt Testing API
Use the Testing API to generate and retrieve test data to verify a subset of flows in non-production environments.
Scroll within the panel for all 13 ·
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.
Bolt Plans Pricing
PLANSRate 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.
Bolt 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.
Bolt Finops
FINOPSSemantic 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.
Bolt Api Context
JSON-LDSpectral Rules 1
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.
Bolt API Rules
SPECTRALJSON Schema 76
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.
account-test-creation-data
JSON SCHEMAaccount-test-phone-data
JSON SCHEMAaccount
JSON SCHEMAaddress-listing
JSON SCHEMAExplicit Address Reference
JSON SCHEMAAddress ID Reference
JSON SCHEMAPartial Address Reference
JSON SCHEMAaddress-reference
JSON SCHEMAamount
JSON SCHEMAauthorization-code-request
JSON SCHEMAbase-oauth-token-response
JSON SCHEMAcart-2
JSON SCHEMAcart-discount
JSON SCHEMAcart-error
JSON SCHEMAcart-item
JSON SCHEMAcart-shipment
JSON SCHEMAcart-updated-event-data
JSON SCHEMAcart
JSON SCHEMAcountry-code
JSON SCHEMAcreate-full-account
JSON SCHEMAcredit-card-error
JSON SCHEMAcredit-card-network
JSON SCHEMAcredit-card
JSON SCHEMAerror
JSON SCHEMAevent
JSON SCHEMAevents-request
JSON SCHEMAevents-response
JSON SCHEMAfailed-event
JSON SCHEMAfield-error
JSON SCHEMAget-access-token-response
JSON SCHEMAguest-payment-initialize-request
JSON SCHEMAitem
JSON SCHEMAmarketplace-commission-fee
JSON SCHEMAorder-response
JSON SCHEMAorder
JSON SCHEMApage-view-event-data
JSON SCHEMApage-viewed-event-data
JSON SCHEMApayment-action-request
JSON SCHEMApayment-completed-event-data
JSON SCHEMApayment-event-data
JSON SCHEMApayment-incremental-authorization-request
JSON SCHEMApayment-initialize-request
JSON SCHEMAAffirm Payment Method
JSON SCHEMAAfterpay Payment Method
JSON SCHEMAApplePay Payment Method
JSON SCHEMACredit Card Payment Method
JSON SCHEMApayment-method-extended
JSON SCHEMAGooglepay Payment Method
JSON SCHEMAKlarna Account Payment Method
JSON SCHEMAKlarna Pay Now Payment Method
JSON SCHEMAKlarna Payment Method
JSON SCHEMAPayPal Payment Method
JSON SCHEMAPayment by reference Method
JSON SCHEMApayment-method
JSON SCHEMApayment-response-finalized
JSON SCHEMApayment-response-pending
JSON SCHEMApayment-response-three-ds-required
JSON SCHEMApayment-response
JSON SCHEMApayment-update-request
JSON SCHEMAprocessor-response
JSON SCHEMAprofile-creation-data
JSON SCHEMAprofile
JSON SCHEMArecognition-event-data
JSON SCHEMArefresh-token-request
JSON SCHEMAseller-info
JSON SCHEMAseller-split-amounts
JSON SCHEMAseller-split
JSON SCHEMAshopper-recognized-event-data
JSON SCHEMAtest-credit-card
JSON SCHEMAthree-ds-error
JSON SCHEMAtransaction-authorization
JSON SCHEMAtransaction-capture
JSON SCHEMAtransaction-refund
JSON SCHEMAtransaction-void
JSON SCHEMAtransaction
JSON SCHEMAupdate-cart-event-data
JSON SCHEMAScroll within the panel for all 76 ·
Examples 11
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.
Accountaddresscreate Request
EXAMPLEAccountaddressedit Request
EXAMPLEOauthgettoken Request
EXAMPLEOrderscreate Request
EXAMPLEOrderscreate Response 200
EXAMPLEPaymentsaction Response 200
EXAMPLEPaymentsinitialize Request
EXAMPLEScroll within the panel for all 11 ·
Security Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Bolt — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bolt · machine-readable index on apis.io