Boosted Commerce · Authentication Profile

Boosted Commerce Authentication

Authentication

Boosted Commerce declares 4 security scheme(s) across its OpenAPI definitions.

CompanyE-CommerceRetailConsumer Packaged GoodsHealth and WellnessSupplementsBeautyAgentic CommerceUniversal Commerce ProtocolMCPShopifyDirect to Consumer
Methods: Schemes: 4 OAuth flows: API key in:

Security Schemes

none
agentIdentity
· in: request body (meta.ucp-agent.profile)
humanInTheLoop
delegatedPayment

Source

Authentication Profile

boosted-commerce-authentication.yml Raw ↑
generated: '2026-08-08'
method: probed
source: https://primelabs.org/agents.md + live unauthenticated POST to https://primelabs.org/api/ucp/mcp
note: >-
  Boosted Commerce publishes no API keys, OAuth client registration, or developer accounts. The
  agent-commerce surface on its brand storefronts is deliberately anonymous: `tools/list` and the
  catalog/cart/checkout tools were exercised with no credentials of any kind. Authorization is not
  carried by a token at all — it is carried by the buyer, at the moment of payment, through a UCP
  payment handler. Absence of an auth scheme here is the design, not a gap.
schemes:
- id: anonymous
  type: none
  applies_to:
  - tools/list
  - search_catalog
  - lookup_catalog
  - get_product
  - create_cart
  - get_cart
  - update_cart
  - cancel_cart
  - create_checkout
  - get_checkout
  - update_checkout
  - cancel_checkout
  - get_order
  evidence: >-
    POST https://primelabs.org/api/ucp/mcp with no Authorization header returned HTTP 200 and a full
    13-tool manifest on 2026-08-08.
- id: ucp-agent-profile
  type: agentIdentity
  in: request body
  parameter: meta.ucp-agent.profile
  required: true
  description: >-
    Every tool call must carry a `meta.ucp-agent.profile` URI identifying the calling agent for UCP
    discovery. This identifies the agent; it does not authenticate or authorize it.
  evidence: '`meta.ucp-agent` is a required property of every one of the 13 tool inputSchemas.'
- id: buyer-approval
  type: humanInTheLoop
  applies_to:
  - complete_checkout
  required: true
  description: >-
    Payment completion requires explicit, contemporaneous buyer approval. Agents that cannot obtain
    it are instructed to route the purchase through Shop Pay via the Shop skill instead.
  evidence: >-
    "Checkout requires human approval. Agents must not complete payment without explicit buyer
    consent." — https://primelabs.org/agents.md
- id: payment-handlers
  type: delegatedPayment
  handlers:
  - id: com.google.pay
    version: '2026-01-11'
  - id: dev.shopify.card
  description: >-
    Payment instruments are supplied through UCP payment handlers declared in the store's
    /.well-known/ucp profile, not through credentials issued by Boosted Commerce.
oauth2: false
openid_connect: false
api_keys: false
mutual_tls: false
docs: https://primelabs.org/agents.md
x-evidence:
- url: https://primelabs.org/api/ucp/mcp
  method: POST
  http_status: 200
  fetched: '2026-08-08'
- url: https://primelabs.org/.well-known/ucp
  http_status: 200
  fetched: '2026-08-08'
- url: https://boostedcommerce.com/.well-known/openid-configuration
  http_status: 403
  fetched: '2026-08-08'

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact
curl "https://apis.io/api/v1/security/boosted-commerce-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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