The declared surface.
Current blockers are known and named. The declared v1 subset covers the product, variant, order, return, inventory, discount, customer, and fulfillment shapes used by the launch scenarios.
Storefront compatibility is covered for the current read surface. Checkout, payments, and broad Storefront mutation families are outside the launch claim.
How we know.
Meguro compares responses, status codes, and error bodies against real Shopify. The WIRE-A, WIRE-B, R-5, and R-7 lineage is the proof path behind the public number.
The grammar is proven once per driver against a real store. Practice-store users inherit that proof instead of spending hours on a dev-store setup loop for every run.
Unsupported calls fail loudly with named errors or userErrors. Meguro does not silently pretend a missing Shopify shape worked.
Measured, not promised.
DEMO-QF measured the launch reference workload on July 7, 2026: 5,945 Shopify API calls, 372 reads, 5,572 writes, 1 blocked call, 365 store days, 24 m 31.5 s sequential. One call at a time, no rate limits.
| Workload | Meguro measurement | Real dev-store comparison |
|---|---|---|
| Light compatibility agent | About 1,500 calls/year; typically 10-20 minutes depending on the agent. | Throttle and round-trip time are the agent's wall-clock floor. |
| Returns triage reference | 5,945 calls in 24 m 31.5 s, sequential, measured July 7, 2026. | Its own calls would be roughly an hour after setup, depending on round trips and backoff. |
| Manufacturing the year | The store year is computed by Meguro and then exercised by the agent. | ~50-70,000 setup API calls, a hard 2-hour throttle floor, realistically a day, and real time still does not pass. |
Replay as final proof.
When platform-grade proof is needed, Meguro replays a receipt's calls onto a real Shopify dev store: exact requests, paced at platform limits, with IDs translated where materialization requires it.
The console flow ships with the App Store release. Today this page states the mechanism and the status plainly: call replay is the final confirmation step, not the everyday practice loop.
What this does not claim.
Meguro reports pre-tax dollars. It is not a payments, tax, invoice, or settlement engine.
The practice world models demand and operations: orders, returns, stock movement, fulfillment pressure, and agent decisions. It does not claim future merchant demand.
Throttle modes are compatibility tools. The default practice lane deliberately does not impose Shopify rate limits.