A PRACTICE STORE FOR YOUR COMMERCE AGENT

We write time.

Meguro is a practice store for your commerce agent, with a year of simulated trading history and a clock you control. Your own agent connects, makes decisions, and advances the store through the scenario. Each run gives you a receipt showing its calls, the changes applied, and anything that was rejected.

You know this store.

Shopify's generated test data is useful sample data, not a store that has lived through a release, a stockout, or a Black Friday. Your agent can read the store's history and act as the scenario unfolds.

What the history includes. The Shopify API returns orders your agent creates by completing draft orders. Background sales and demand are simulated and do not appear as Shopify orders.

A free development storeA Meguro practice store
No lived order history; ordinary app-created orders cannot be backdated into oneA year of simulated sales and demand, ready when your agent connects
Completing draft orders can lock checkoutYour agent can complete draft orders without locking checkout
Real platform rate limits constrain repeated and parallel runsMeguro uses the standard-1000 modeled request-cost bucket by default; it is not exact Shopify rate-limit parity

Below is one of those years. Scroll through it.

JUN 2025 — RUN BEGINS · SEED demo:meguro
06
JUN2025

A new store gets its first memory.

Six products, one seed, and the first dated simulated sale — modeled history available through Meguro's ledger, impact, and receipts. From there the year computes day by day — month curves, weekday shape, week-to-week drift — not sampled from a recording, not a random number generator on a treadmill.

02:14 order #1561 · 2× Core Tee · processedAt 2025-06-10 · paid ✓
sat +31% · sun +24% · weekly drift φ=0.6 · all from seed demo:meguro
120
OCT 042025

Your agent steps in.

A run begins mid-history: your agent connects to a store that has already lived, reads the books as it finds them — and then it writes. From here, store time advances only as your run drives it, and everything it changes feeds the weeks that follow.

run opens · store day 120 · every call recorded · agent writes stay attributable
×3.1
NOV 282025

Black Friday.

DEMAND ×3.1 · CARTS SPIKE · WEBHOOKS SWARM · THE STORE HOLDS

Velocity climbed all autumn; the hoodie's cover-days shrank from 41 to 17, and your agent adjusted available inventory before cover hit zero. Now the biggest day of the synthetic year lands exactly where the declared calendar puts it — and the shelves hold because of an October decision. See how your agent carries this scenario's November before a release reaches a merchant.

SKU FLEECE-03 · cover 41d → 17d · available inventory adjusted ✓ · restock day 148
01
JAN2026

The slump. Also on purpose.

January is slow in real stores, and it is slow here: a post-promo dip, slower weeks, the unglamorous data that makes forecasts honest. The dip makes the cost of excess inventory visible.

week 02 · −38% vs dec peak · returns logged · nothing fired that shouldn't
04
APR2026

Stockouts, restocks, receipts.

The tank sells out. A restock lands. Every webhook arrives once, in order — and Meguro records the calls and changes so the sequence stays inspectable.

inventory 7→0→52 · restock recorded · webhooks ✓ once, in order
JUN 2025 0%

Meguro publishes its supported Shopify API operations and limitations. The Exam replays the recorded requests on your Shopify development store and records Shopify's answers.

Shopify coverage

1seed — change it, get a different year

Trace an unexpected result back to the actions that produced it.

MEGURO — RUN RECEIPTworld winback-proof-d · 120 store days · A21-winback
calls recorded-
reads-
writes applied-
writes blocked — named, never silent-
state changes attributed-
scenario-local run record · not a merchant demand claim

Share the record with your team when you need another person to investigate.

Receipt verification

Your pipeline can check the receipt and fail when a required action was rejected or nothing was observed. Silence never passes.

Integration guide

YOUR AGENT

Speaks MCP. Claude Code is the tested client. Meguro serves MCP 2025-06-18 over Streamable HTTP; OAuth 2.1 with dynamic client registration and PKCE; RFC 9728 protected-resource discovery on the 401. Or it swaps one URL and keeps speaking the Shopify Admin grammar it already knows. Either way, unsafe writes are refused and named, and nothing changes outside a run.

YOUR TEAM

The dashboard: worlds, runs, receipts, ledgers — watch a year being written from a browser tab.

YOUR CI

One script, exit codes, no SDK; every pipeline run ends holding a receipt.

Connect your agent

Questions, answered

The practical details.

How do I create test orders in a Shopify development store?

Generated test orders arrive as drafts, and completing drafts can lock checkout. A Meguro practice store provides a year of simulated sales and demand, orders your agent completes from drafts, and a receipt of every call your software makes.

Can I generate order history with past dates?

Yes, inside a Meguro practice store. A seeded year provides simulated sales and demand for past dates. These do not appear as Shopify orders.

Is this a mock of the Shopify API?

Practice speaks the Shopify grammar Meguro has measured. The Exam records Shopify's answers for recorded requests on one development store; it does not decide whether the agent was right. Current coverage is 43/55 Admin GraphQL checks (measured june 2026), with the supported and unsupported boundary published in full.

Can I test an AI agent safely?

Practice stores are isolated, deterministic, and disposable. Unsafe writes are blocked and named, exploratory probes stay distinct from agent activity, and the receipt records both accepted and rejected calls.

What about webhooks?

Computed events can deliver signed webhooks for orders, inventory changes, and restocks. The receipt records delivery and rejection evidence so failures are visible rather than inferred.

How is this different from sample-data apps or staging clones?

Seeders and clones provide useful state at one moment. Meguro adds declared time, repeatable scenarios, receipts, and release gates so software can simulate a sequence of commerce events.

Does it work in CI?

Yes. One script, no SDK, and exit codes suitable for a deployment gate. Your app or agent connects with the same three Shopify values it already expects.

What does it cost?

Meguro has a permanent Free tier, with paid tiers above it — Solo, Builder, and Team. Current prices are on the pricing page.

GET STARTED

Give your agent a task.

Paste the prompt into your agent to start a practice scenario.