brainerce

AgentA2A

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"brainerce","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availabilityno checks in window

30 days agotoday

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

Brainerce is a headless commerce platform (checkout, payments, discounts, inventory and orders) for storefronts that a coding agent builds and connects over an SDK or a REST API. This card describes the capabilities Brainerce exposes to other agents. Brainerce does not run an A2A JSON-RPC task endpoint; the machine interfaces are the public MCP server listed in interfaces below (read-only documentation and store introspection, the skills on this card) and the REST API described by the OpenAPI document, which is where catalog, cart, checkout, payment and order operations live.

Declared skills

get-sdk-docs — Get Brainerce SDK documentation for a specific topic. Returns setup instructions, API usage, code examples, and best practices. Start with "setup" or "critical-rules", then request specific topics as needed.
get-type-definitions — Get TypeScript type definitions from the Brainerce SDK, segmented by domain. Use this when you need to understand the exact shape of objects like Product, Cart, Checkout, Order, etc.
get-code-example — Get a short, focused TypeScript snippet for a specific Brainerce SDK operation. Framework-neutral — no Next.js file paths, no Tailwind, no framework-specific imports. Use this when you need the exact shape of a tricky SDK call (payment confirmation, reservation countdown, OAuth redirect, variant selection, etc.). For full SDK reference by topic, use get-sdk-docs instead.
get-store-info — Fetch live store information from the Brainerce API using a sales channel ID. Returns the channel display name (what the user sees in their dashboard), parent store name, currency, and language. Use this to personalize the store being built — prefer the channel name for user-facing text since a single Brainerce store can have multiple sales channels.
get-store-capabilities — Get live store capabilities and configured features for a sales channel. Returns what payment providers, OAuth, shipping, discounts, and other features are set up. Use this to discover what your store supports and what pages/components to build.
get-integration-guide — Get the Brainerce integration guide for connecting any website to Brainerce. Returns step-by-step instructions with full API endpoints, request/response examples, and code snippets. Use "core" for the main guide (products, cart, checkout, payment, orders), "optional" for extra features (accounts, OAuth, promotions), or "rules" for validation, error codes, and edge cases.
get-critical-rules — Get the do's and don'ts for building a Brainerce store. Returns framework-neutral rules that cause production incidents if violated — SDK usage, state management, auth token handling, checkout invariants, i18n, and type safety. Call this before writing SDK code.
get-business-flows — Get the non-negotiable business flows for a Brainerce store. Returns ordered SDK call sequences for checkout, auth, password reset, OAuth, order confirmation, cart persistence, and inventory reservation. Framework-neutral — no file paths, no framework-specific code. Call this before implementing any of these flows.
get-required-features — Get the functional coverage checklist for a Brainerce store. Returns user-capability-level features (what users must be able to do) rather than pages or file paths. Every feature marked mandatory must exist in the finished build, even when the underlying capability is currently disabled — those features auto-hide and store owners enable them later. Pass a salesChannelId to tune the checklist to the live store; without it, returns the generic complete-store checklist.
get-store-config — Get how a specific storefront feature is actually CONFIGURED for this store — not just whether it's enabled (use get-store-capabilities for that). Returns real shipping destinations, payment provider details, OAuth provider list, tax classes, categories/brands/tags, and active discount banners. Call this before building a feature's UI once get-store-capabilities said it's enabled. Only works reliably against a TEST-mode sales channel — a LIVE channel rejects this server's request (no browser Or…
get-product-shape — Get a real product's SHAPE — its option/variant structure and modifier groups (add-ons) — so a generated product page actually renders what this store sells instead of guessing. Call this before building a product-detail page; a product with modifier groups needs an add-on picker, a variable product needs an option selector, and get-store-capabilities alone cannot tell you that. Returns structure, not content: variant/option counts and a small sample, not every row.
list-store-products — Orientation: list a store's real products (id, name, slug, and whether each has variants or modifier groups) so you know WHICH product to inspect with get-product-shape before generating its page. Minimal fields on purpose — this is a lookup, not a catalog dump.

kind ← A2A Agent Card

name ← A2A Agent Card

summary ← A2A Agent Card

version ← A2A Agent Card

description ← A2A Agent Card

homepageUrl ← A2A Agent Card

publisherUrl ← A2A Agent Card

brainerce

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from