MEGURO Docs
Documentation

Task-oriented technical guidance for practice, evidence, automation, and verification.

Reference and troubleshooting

API and runner reference

Public control, runner, receipt, and schema contracts.

Scope and proof boundaries

These identifiers and routes are legitimate public integration material. A runner controls one bounded practice lifecycle; it does not grant Shopify production access or verify a receipt result.

Identity and credentials

  • storeId identifies the practice store; worldId remains an accepted compatibility alias.
  • attemptId identifies the run returned by start and is used by later lifecycle calls.
  • Control calls use the workspace API key; the agent receives only the separate Admin URL and per-store token.

Runner lifecycle

ActionHTTP routeMCP tool
StartPOST /practice/stores/{storeId}/playbackspractice_run_start
StatusGET /practice/playbacks/{attemptId}/statepractice_run_status
CheckpointPOST /practice/playbacks/{attemptId}/checkpointpractice_run_checkpoint
AdvancePOST /practice/playbacks/{attemptId}/advancepractice_run_advance
FinishPOST /practice/playbacks/{attemptId}/finishpractice_run_finish
ReceiptGET /practice/playbacks/{attemptId}/reportpractice_run_report

Advance accepts exactly one of days or until. Copy the current server-owned practiceRun.advanceCursor object unchanged; legacy flat expectedDay and expectedCallSeq request fields remain compatible.

Schemas and artifacts

Read Receipt schema v1 for the rendered receipt schema. Public temporal exports are allowlisted summaries; private exports contain bounded internal-forensics material and belong in restricted artifacts. Same scenario, seed, clock, and agent calls produce the same modeled result; changed inputs create new evidence rather than rewriting an old receipt.

Advanced Store-time contracts

Code-controlled runners use short-lived one-time grants bound to one workspace, store, run, current Store-time coordinate, immutable revision, and command digest. Temporal requirements are versioned JSON arrays evaluated against recorded calls and scenario time. Changing a requirement produces a new immutable revision; eligibility for Shopify Exam remains an explicit later decision rather than an effect of choosing a clock.