---
skill_id: x402-merchant-operating-system
evaluation: free
price_usd_full: 0.099
challenge: https://lvlltd.com/api/pay?skill=x402-merchant-operating-system
outline: https://lvlltd.com/skills/x402-merchant-operating-system/outline.json
standards: x402, ERC-7857
---

# Free sample — x402 Merchant Operating System

**Skill ID:** `x402-merchant-operating-system`  
**Full unlock:** $0.099 USDC via x402 on Base  
**Challenge:** https://lvlltd.com/api/pay?skill=x402-merchant-operating-system  
**Outline JSON:** https://lvlltd.com/skills/x402-merchant-operating-system/outline.json

## Summary

Scaffolding for running an x402 skill market: a validated plan/checklist runtime plus a written spec (detail.md). It does not execute anything; you implement the steps.

## When to use

- Launching or professionalizing an x402 skill market
- You want a step list and checklist to implement yourself, not an executor
- Aligning product, finance, and support on confirmed revenue only

## Decision criteria (buy vs skip)

- You need this when: Launching or professionalizing an x402 skill market
- You get capability: plan(goal): returns the 5 runbook steps above with status pending
- Budget fits: full unlock is $0.099 USDC on Base
- You can automate unlock via HTTP 402 without a browser
- You only need teaser/outline first — sealed src/ops stay locked until payment

## Outline (preview)

1. intake: Intake goal + constraints (SSI/PASS + Super Alignment guidelines)
2. plan: Plan steps with done_when
3. execute: Execute domain method from detail.md (you implement this)
4. verify: Verify outputs + claim scrub (you implement this)
5. ship: Emit artifacts + next_actions

## Capabilities (preview)

- plan(goal): returns the 5 runbook steps above with status pending
- checklist(goal): returns the done_when checklist for those steps
- run({ goal }): dry run by default; returns plan + checklist with steps skipped and executed:false
- run({ goal, dry_run: false }): returns ok:false, executed:false and every step not_executed; nothing is performed
- Input validation (goal, tenantId, agentId, dry_run) with structured invalid_input errors
- Tool schemas (listTools/executeTool) for your agent registry

## What you get after payment

- src/index.js, src/tools.js, src/runbook.js: plan/checklist scaffold runtime (never executes steps)
- schemas/output.schema.json: result shape (step status pending | skipped | not_executed)
- detail.md: the specification you implement
- README.md, SKILL.md, LICENSE.md, package.json, agent-install.json, pack-files.json

## Not included

- No automated execution: payments, catalog, ledger, support and dispute work are yours to implement
- No readiness scorecard, metrics, dashboards or domain artifacts beyond the plan + checklist
- SSI/PASS and Super Alignment are review checklists, not enforced protections

## Agent buy path (zero human UI)

```
GET  https://lvlltd.com/skills/x402-merchant-operating-system/outline.json
GET  https://lvlltd.com/api/pay?skill=x402-merchant-operating-system   → HTTP 402
# transfer maxAmountRequired USDC to payTo on Base
POST https://lvlltd.com/api/pay
  X-PAYMENT: {"txHash":"0x…","skill":"x402-merchant-operating-system"}
# response.sealed_pack.files = full pack
```

## Sample excerpt

### What `run({ goal, dry_run: false })` returns

```json
{
  "ok": false,
  "executed": false,
  "status": "not_executed",
  "steps": [{ "id": "intake", "status": "not_executed" }, "…4 more, all not_executed"],
  "message": "Not executed: this pack is scaffolding. …implement the execution steps yourself from detail.md…"
}
```

The default is `dry_run: true` (steps `skipped`, `executed: false`). The pack never marks a step done.