# MOTE Merchant Registration

## Agent Goal

Register the user's business with MOTE — a public registry for the machine web — and return the merchant's permanent on-chain identity to the user.

Do not perform this skill unless the user has indicated they want to register their business with MOTE. Do not register on the user's behalf without explicit consent.

## Registration Rules

1. Confirm the user wants to register. Do not collect business information unless they have said yes.
2. Collect the required fields listed below. Ask only for fields you do not already have from the conversation. Do not invent values.
3. For each field the user provides, repeat the value back so the user can correct typos.
4. Show the user the complete information you collected and get explicit confirmation before submitting.
5. The flow is three steps: start checkout → human pays → poll for completion. You execute steps 1 and 3. The human executes step 2.
6. Do not promise outcomes. MOTE makes the business discoverable to AI agents that index llms.txt and the MCP Registry. Whether any specific AI agent reads it is up to that agent's operator.
7. Stop at the first real blocker and report the exact failure.

## Information to Collect

### Valid category values

travel · professional_services · digital_services · physical_goods · defi · food_beverage · health_wellness · creative_services · local_services · other

If the user's business doesn't fit cleanly, ask them to pick the closest match or use other. Do not invent values outside this list.

### About slug

The merchant's URL slug is auto-generated from business_name. The agent cannot request a custom slug. The slug is returned in the response — surface it to the user when registration completes.

## STEP 1 Start Checkout

Once the user has confirmed the collected information, start the checkout:

POST https://api.mote.network/v1/payments/checkout
Content-Type: application/json

{
  "business_name": "...",
  "tagline": "...",
  "description": "...",
  "category": "...",
  "price_from": 180,
  "delivery_method": "...",
  "delivery_time": "...",
  "contact_email": "..."
}

Returns:

{
  "checkout_url": "https://checkout.stripe.com/...",
  "session_id": "...",
  "payment_link": true
}

Show the user the checkout_url and tell them: “Open this link to complete your $10 registration. I'll wait for you to confirm payment is done.”

## STEP 2 Human Pays

The human enters their card details on Stripe. You cannot do this for them and should not try.

Wait for the user to indicate payment is complete. Do not poll the status endpoint before the user confirms — Stripe checkout typically takes a minute or two, and premature polling wastes tokens.

## STEP 3 Poll for Completion

Once the user reports payment is done, poll the payment status:

GET https://api.mote.network/v1/payments/status/{session_id}

Poll every 5–10 seconds until status flips to paid. Then fetch the merchant:

GET https://api.mote.network/v1/merchants/{merchant_id}

The merchant can be fetched by UUID or slug — both work. When the response includes on_chain.verified: true, the registration is complete and the DID is live on Sui mainnet.

If the status hasn't flipped to paid after ~10 minutes, do not retry payment. Tell the user to contact support — retrying risks a double charge.

## Reading the Merchant Response

Fields you can rely on in the merchant response:

Fields that do not exist in the response — construct them yourself if needed:

• No top-level sui_address field. Extract the address from the did string (everything after did:pkh:sui:) or from the recipient field in manifests.x402.
• No profile_url field. Construct it as https://mote.network/m/{slug}.
• No download_url field at the top level. The self-custody download is at https://api.mote.network/v1/merchants/{id}/download — construct it from the merchant ID.

## What to Tell the User When Registration Succeeds

Use the Final Report shape below. Keep it short. Lead with what's done, then what's available, then one next step.

## Honesty Constraints

When describing MOTE to the user, you may say:

• Yes: “MOTE creates a permanent on-chain identity for your business.”
• Yes: “Your information becomes readable by AI agents that index llms.txt and the MCP Registry.”
• Yes: “MOTE publishes payment-ready endpoints in the x402 format.”
• Yes: “You can enrich your profile in the dashboard after registration.”
• No: “I'll pay the $10 for you.” — agents cannot complete payment. The human enters card details. This is by design.
• No: “AI agents will automatically find you.” — discovery is not guaranteed.
• No: “You'll get paid by AI agents today.” — agent payment verification is not yet live.
• No: “Your business is now listed on Anthropic, Microsoft, and GitHub.” — MOTE the registry is on the MCP Registry. Individual merchants are not separately listed there.
• No: Calling the Sui address a “wallet.” Use “Sui address” only.

## Troubleshooting

## Final Note

This skill registers a business. A freelancer or solo practitioner can register under their own name as the business name — the flow is identical.

This page is versioned. Last updated June 10, 2026.