Developers

Build with your Micro account: conversations, inbox and work. For individual services, use the HTTP API reference or MCP tools catalogue. x402 explains wallet-paid access to public services.

Use the same resources from your browser or your own code. Send JSON with Content-Type: application/json and request JSON with Accept: application/json.

Agent

Create a token with Agents and Allow actions. Set it as MICRO_TOKEN, then run:

curl 'https://m3o.com/agent' \
  -H "Authorization: Bearer $MICRO_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"prompt":"Help me plan my week"}'

The response contains text and thread. Send {"prompt":"Focus on Monday","thread":"THREAD_ID"} to continue. Use /agent/name for a named agent. Keep your token outside browser code and source control.

Inbox and Work

Use the same authorization header and enable the corresponding capability on your token. Writes also require Allow actions.

Request	Purpose
GET /inbox	Read your inbox as JSON.
GET /inbox?id=THREAD_ID	Read a thread.
POST /inbox	Send {"action":"mark_read","id":"THREAD_ID"} or mark_unread.
GET /work	List delegated work; filter with ?status=failed.
GET /work?id=WORK_ID	Read progress in the work field.
POST /work	Send {"prompt":"…"} to submit work, or {"action":"retry","id":"WORK_ID"} to retry reviewed work.

Do not automatically retry a submission after a lost response: it may already have started. Usage draws from the same account allowance and balance.

Tools

Tools documents the runtime services available through /mcp and /api/v1. Use a Services token for these. MCP supplies tools to your client; it does not run your Micro agent.

x402

Use public services with wallet payments through the machine-readable host. Connection details and payment flow.