Agent-Ready Commerce
Mika is agent-ready because its visible storefront state, operation metadata, and public manifests can agree.
Agent-ready does not mean Mika is a hosted agent runtime. Mika does not issue OAuth tokens, run MCP servers, process payment rails, or verify AP2 mandates.
The Glossary defines the repeated boundary terms used here: public, trusted, admin, hidden, projection, operation descriptor, sellable, content ref, and idempotency key.
The semantic core includes catalog, sellables, prices, variants, stock, cart, wishlist, checkout handoff, account, subscription, order, download, provider refs, actor context, proof refs, and idempotency posture.
What “Agent-Ready” Means Here
Section titled “What “Agent-Ready” Means Here”Agent-ready means the same operation registry can describe:
- public storefront facts for crawlers and LLMs;
- host-owned trusted flows such as cart quote or checkout preview;
- admin-only operations such as stock adjustment or refunds;
- hidden service operations such as provider webhooks.
The package can produce descriptors and manifests for those semantics. The host still owns the runtime boundary: who may call a tool, how the actor is authenticated, what confirmation is required, how retries are deduplicated, and how provider/payment state is verified.
Public Manifest Boundary
Section titled “Public Manifest Boundary”createMikaAgentManifest() defaults to the public and trusted visibility groups. That is useful source material for a protected projection, but it is not automatically safe to publish as a public tool list.
The copied /.well-known/mika-agent.json endpoint deliberately calls createMikaAgentManifest({ include: ["public"] }). That public endpoint should expose route hints for safe catalog and stock reads, plus summaries of protected flows, while leaving checkout, account, order, admin, payment, and tool execution behind host-owned authorization and confirmation.
Related Tasks
Section titled “Related Tasks”- Agent-Ready Storefront shows the public metadata path.
- LLMs And Manifest shows copied metadata endpoints.
- Agent Manifest lists exact manifest helpers and visibility filters.
Source Anchors
Section titled “Source Anchors”- ⓟ
../emdash-mika/docs/agentic/README.md - ⓟ
../emdash-mika/src/agent.ts - ⓟ
../emdash-mika/src/api/operation-agent-metadata.ts - ⓐ
../emdash-mika/src/templates/astro/examples/agent-ready-storefront.md - ⓐ
../emdash-mika/src/templates/astro/pages/.well-known/mika-agent.json.ts