BlueCart
BlueCart is an end-to-end eCommerce and procurement platform for the hospitality and food and beverage industries, connecting restaurants and buyers with wholesale distributors and suppliers. It streamlines wholesale ordering, order management, inventory, and payments for both sides of the supply chain. BlueCart exposes a public REST API that lets distributors and partners programmatically manage products, orders, customers, catalogs, and users, returning JSON responses and integrating BlueCart data with external accounting, eCommerce, and logistics systems used across foodservice operations.
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 BlueCart the way a machine reads it — 72 machine-readable artifacts across 5 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 — BlueCart scores 55.6/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 BlueCart
Each block below is one kind of artifact we hold for BlueCart. 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 5
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.
BlueCart Catalogs API
Manage client-specific catalogs of products and pricing.
BlueCart Clients API
Manage buyer/client associations and their account details.
BlueCart Orders API
Search, retrieve, place, and modify wholesale orders.
BlueCart Products API
Manage the product catalog including pricing and inventory.
BlueCart Users API
Manage platform users and their roles and notifications.
Open 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).
BlueCart API
OPEN COLLECTIONPricing 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.
Bluecart 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.
Bluecart 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.
Bluecart Context
JSON-LDSpectral Rules 2
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.
BlueCart API Rules
SPECTRALBlueCart API Rules
SPECTRALJSON Schema 19
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.
CatalogCreate
JSON SCHEMACatalogList
JSON SCHEMACatalog
JSON SCHEMACatalogUpdate
JSON SCHEMAClientCreate
JSON SCHEMAClient
JSON SCHEMAClientUpdate
JSON SCHEMAOrderCreateResult
JSON SCHEMAOrderCreate
JSON SCHEMAOrderList
JSON SCHEMAOrderProduct
JSON SCHEMAOrder
JSON SCHEMAOrderUpdate
JSON SCHEMAProductCreate
JSON SCHEMAProductList
JSON SCHEMAProduct
JSON SCHEMAUserCreate
JSON SCHEMAUserList
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Bluecart Catalog Create Structure
JSON STRUCTUREBluecart Catalog List Structure
JSON STRUCTUREBluecart Catalog Structure
JSON STRUCTUREBluecart Catalog Update Structure
JSON STRUCTUREBluecart Client Create Structure
JSON STRUCTUREBluecart Client Structure
JSON STRUCTUREBluecart Client Update Structure
JSON STRUCTUREBluecart Order Create Result Structure
JSON STRUCTUREBluecart Order Create Structure
JSON STRUCTUREBluecart Order List Structure
JSON STRUCTUREBluecart Order Product Structure
JSON STRUCTUREBluecart Order Structure
JSON STRUCTUREBluecart Order Update Structure
JSON STRUCTUREBluecart Product Create Structure
JSON STRUCTUREBluecart Product List Structure
JSON STRUCTUREBluecart Product Structure
JSON STRUCTUREBluecart User Create Structure
JSON STRUCTUREBluecart User List Structure
JSON STRUCTUREBluecart User Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
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.
Bluecart Catalog Example
EXAMPLEBluecart Client Example
EXAMPLEBluecart Order Example
EXAMPLEBluecart Order List Example
EXAMPLEBluecart Product Example
EXAMPLEBluecart User Create Example
EXAMPLEBluecart User Example
EXAMPLEBluecart User List Example
EXAMPLEScroll within the panel for all 19 ·
Security 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 BlueCart — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 2
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/bluecart · machine-readable index on apis.io