Skip to content
Emdash Mika Docs

Overview

Mika is agent-ready commerce for content-led Astro and EmDash storefronts. In practical terms, it gives a host storefront commerce contracts, form actions, provider boundaries, and metadata that humans, crawlers, and agents can read consistently.

It provides typed commerce primitives, Astro Actions, route contracts, provider interfaces, operation descriptors, and copyable Astro template files for storefronts that need products, variants, stock, carts, wishlists, checkout handoff, account links, subscriptions, downloads, licenses, provider webhooks, and agent-readable metadata.

Mika is not a full commerce platform. The host app owns product content, routing, layout, auth/session policy, provider credentials, tax and shipping rules, rate limits, deployment, support, and protected agent/tool surfaces.

Keep one rule in mind while reading these docs: Mika exports contracts and copyable files; the host Astro project decides where those files live and how requests are allowed to move through them.

Use the Integration File Map whenever a guide mentions astro.config.mjs, src/actions/, copied template pages, EmDash plugin routes, or provider wiring.

Where Examples Come From

Section titled “Where Examples Come From”

Most examples in these docs are one of three things:

  • Package exports from ../emdash-mika/package.json, such as @bnomei/emdash-mika/astro, @bnomei/emdash-mika/astro-actions, @bnomei/emdash-mika/server, and @bnomei/emdash-mika/stripe.
  • Copyable Astro files from ../emdash-mika/src/templates/astro/**, which become host-owned src/actions, src/pages, src/components, src/lib, and src/styles files after copying.
  • Runnable host-app examples from ../emdash-mika-template/**, which show how those copied files fit into an Astro + EmDash project.

When a guide shows a path under src/, read it as a host app path unless the guide explicitly says it is inside the package template source.

Section titled “What To Read Next”

For a first look, read and run:

  1. Compatibility And Publication to choose local workspace or published install mode.
  2. Quickstart: Seeded Template to run a complete source-backed host app.

For an existing Astro + EmDash app, continue with:

  1. Install to register the plugin and identify the host-owned API and Actions files.
  2. First Product Page to connect one host route to Mika sellables.
  3. First Integration Checklist to verify the first integration slice.

Then choose a deeper path:

Use Mika When

Section titled “Use Mika When”
  • You have content-led product pages and need commerce behavior next to them.
  • You want Astro-native HTML forms and Actions instead of a hidden app route system.
  • You need public product metadata that agrees with visible price, availability, and variant state.
  • You want semantic operation descriptors that can later project into ACP, UCP, MCP, OpenAPI, or other host-owned protocols.

Source Anchor Key

Section titled “Source Anchor Key”

Source anchors use these glyphs to separate the main source sets:

  • ⓟ core package repo: ../emdash-mika/**.
  • ⓐ copyable Astro template files inside the core package: ../emdash-mika/src/templates/astro/**.
  • ⓣ seeded GitHub template repo: bnomei/emdash-mika-template, local path ../emdash-mika-template/**.

External References

Section titled “External References”

Source Anchors

Section titled “Source Anchors”
  • ⓟ ../emdash-mika/package.json
  • ⓟ ../emdash-mika/README.md
  • ⓐ ../emdash-mika/src/templates/astro/examples/release-slice.md
  • ⓣ ../emdash-mika-template/README.md