Hero Bread

Hero Bread is an American food-technology company that makes low-net-carb, high-fiber, zero-sugar baked goods — sliced breads, tortillas, buns, rolls and bagels — sold direct-to-consumer from hero.co and through grocery and foodservice retail. It is not a developer-tools company and publishes no developer portal, OpenAPI description or API documentation. It does, however, operate a live agent-commerce surface on its own storefront subdomain: shop.hero.co serves an llms.txt and an agents.md, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, and an unauthenticated MCP endpoint at /api/ucp/mcp exposing thirteen catalog, cart, checkout and order tools — a Shopify platform capability exposed on the merchant's own host against the merchant's own catalog.

Hero Bread is listed with 1 API on the APIs.io network. Tagged areas include Company, Food and Beverage, Consumer Packaged Goods, Retail, and E-Commerce.

Hero Bread’s developer surface includes documentation, support, engineering blog, pricing, authentication, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

25.0/100 emerging ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent Heartbeat 62/100 slowing saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

1 API 1 MCP Servers 2 Agent Skills

Company Food and Beverage Consumer Packaged Goods Retail E-Commerce Agentic Commerce MCP Universal Commerce Protocol Shopify Direct to Consumer

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 25.0/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 5.2 / 17

Access Clarity 6.2 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 4.3 / 15

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/hero-bread/"><img src="https://apis.io/badge/hero-bread/card.svg" alt="Hero Bread on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Developer Ergonomics scores 30.4 — up to +13.9 composite points Ask about this →
Operational Transparency scores 0.0 — up to +13.0 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/hero-bread/apis.yml: open an issue on github.com/api-evangelist/hero-bread to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Hero Bread Storefront Agent Commerce (UCP/MCP)

The agent-facing commerce interface for the Hero Bread online store. An MCP server at https://shop.hero.co/api/ucp/mcp implements the Universal Commerce Protocol shopping servic...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Hero Bread MCP Server

Remote MCP server at shop.hero.co; 13 tools listed.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Read the Hero Bread catalog without transacting

AGENT SKILL

Buy Hero Bread products as an agent

AGENT SKILL

Hero Bread API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Hero Bread Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Hero Bread Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hero Bread Authentication

none/http/oauth2/openIdConnect · 5 schemes

SECURITY

Hero Bread Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hero Bread Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

WellKnown

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

DataModel

Conformance

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: hero-bread
name: Hero Bread
description: 'Hero Bread is an American food-technology company that makes low-net-carb, high-fiber, zero-sugar baked goods
  — sliced breads, tortillas, buns, rolls and bagels — sold direct-to-consumer from hero.co and through grocery and foodservice
  retail. It is not a developer-tools company and publishes no developer portal, OpenAPI description or API documentation.
  It does, however, operate a live agent-commerce surface on its own storefront subdomain: shop.hero.co serves an llms.txt
  and an agents.md, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, and an unauthenticated MCP endpoint
  at /api/ucp/mcp exposing thirteen catalog, cart, checkout and order tools — a Shopify platform capability exposed on the
  merchant''s own host against the merchant''s own catalog.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: covered
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
image: https://cdn.sanity.io/images/85daklna/production/028e6f6b81bdfad5074d500c93636f8f18866203-2000x1670.webp
url: https://raw.githubusercontent.com/api-evangelist/hero-bread/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: agent-commerce-surface
specificationVersion: '0.20'
created: '2026-08-22'
modified: '2026-08-22'
tags:
- Company
- Food and Beverage
- Consumer Packaged Goods
- Retail
- E-Commerce
- Agentic Commerce
- MCP
- Universal Commerce Protocol
- Shopify
- Direct to Consumer
tags_raw:
- Company
- Food and Beverage
- Consumer Packaged Goods
- Retail
- E-Commerce
- Agent Commerce
- Model Context Protocol
- Universal Commerce Protocol
- Shopify
- Direct to Consumer
apis:
- aid: hero-bread:hero-bread-ucp-mcp
  name: Hero Bread Storefront Agent Commerce (UCP/MCP)
  description: The agent-facing commerce interface for the Hero Bread online store. An MCP server at https://shop.hero.co/api/ucp/mcp
    implements the Universal Commerce Protocol shopping service (dev.ucp.shopping) with thirteen tools spanning catalog search
    and lookup, cart create/read/ update/cancel, checkout create/read/update/complete/cancel, and order read. tools/list answers
    anonymously; tools/call requires a resolvable UCP agent profile and, for transactional tools, a Shopify agent JWT. complete_checkout
    requires an idempotency key and, per the store's own published rules, explicit contemporaneous buyer approval before payment.
  humanURL: https://shop.hero.co/agents.md
  baseURL: https://shop.hero.co/api/ucp/mcp
  tags:
  - Agentic Commerce
  - Catalog
  - Cart
  - Checkout
  - Order
  tags_raw:
  - Agent Commerce
  - Catalog
  - Cart
  - Checkout
  - Orders
  properties:
  - type: Documentation
    url: https://shop.hero.co/agents.md
  - type: MCPServer
    url: mcp/hero-bread-mcp.yml
  - type: LLMsTxt
    url: llms/hero-bread-llms.txt
  - type: Authentication
    url: authentication/hero-bread-authentication.yml
  - type: OAuthScopes
    url: scopes/hero-bread-scopes.yml
  - type: Conventions
    url: conventions/hero-bread-conventions.yml
  - type: Idempotency
    url: conventions/hero-bread-conventions.yml
  - type: ErrorCatalog
    url: errors/hero-bread-problem-types.yml
  - type: DataModel
    url: data-model/hero-bread-data-model.yml
  - type: Conformance
    url: conformance/hero-bread-conformance.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.hero.co/
- type: Documentation
  url: https://shop.hero.co/agents.md
- type: Support
  url: https://www.hero.co/contact
- type: Blog
  url: https://www.hero.co/blog
- type: Pricing
  url: https://www.hero.co/products
- type: Login
  url: https://shop.hero.co/account/login
- type: TermsOfService
  url: https://www.hero.co/terms
- type: PrivacyPolicy
  url: https://www.hero.co/privacy
- type: MCPServer
  url: mcp/hero-bread-mcp.yml
- type: ToolCrosswalk
  url: mcp/hero-bread-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/hero-bread-llms.txt
- type: WellKnown
  url: well-known/hero-bread-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/hero-bread-authentication.yml
- type: OAuthScopes
  url: scopes/hero-bread-scopes.yml
- type: Conventions
  url: conventions/hero-bread-conventions.yml
- type: Idempotency
  url: conventions/hero-bread-conventions.yml
- type: ErrorCatalog
  url: errors/hero-bread-problem-types.yml
- type: DataModel
  url: data-model/hero-bread-data-model.yml
- type: Conformance
  url: conformance/hero-bread-conformance.yml
- type: Lifecycle
  url: lifecycle/hero-bread-lifecycle.yml
- type: Plans
  url: plans/hero-bread-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hero-bread-rate-limits.yml
- type: Packages
  url: packages/hero-bread-packages.yml
- type: DomainSecurity
  url: security/hero-bread-domain-security.yml
x-enrichment:
  date: '2026-08-22'
  status: enriched
  artifacts_added: 25
  pass: local-v1
x-coverage:
  state: covered
  reason: agent-commerce-surface-live
  detail: Hero Bread ships no developer program, but its storefront host shop.hero.co serves a live, anonymously-discoverable
    UCP merchant profile and an MCP endpoint whose tools/list returned 13 real tools with JSON Schema input contracts.
  evidence:
  - url: https://shop.hero.co/.well-known/ucp
    status: 200
  - url: https://shop.hero.co/api/ucp/mcp
    status: 200
  - url: https://shop.hero.co/llms.txt
    status: 200
  - url: https://www.hero.co/.well-known/agent-card.json
    status: 404
  checked: '2026-08-22'

Hero Bread API — frequently asked questions

Does Hero Bread have an API?

Yes. APIs.io lists 1 API from Hero Bread, including Hero Bread Storefront Agent Commerce (UCP/MCP).

How do I authenticate with the Hero Bread API?

Hero Bread documents its authentication (none/http/oauth2/openIdConnect · 5 schemes). The details are profiled on APIs.io as Hero Bread Authentication.

Does Hero Bread have an MCP server?

Yes. APIs.io lists 1 MCP server for Hero Bread: Remote MCP server at shop.hero.co; 13 tools listed.

Is the Hero Bread API ready for AI agents?

Hero Bread has a Kin Score of 25.0 out of 100 (emerging) and an Agent Readiness score of 27.0 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/hero-bread"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hero-bread/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hero-bread/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.