micro
Get started

MICRO FOR DEVELOPERS

More capabilities.
One integration pattern.

Discover tools, authorize a request and retrieve the result.
The same account, balance and order contract across providers.

Follow the quickstart API reference
CREATE AN ORDERSERVER-SIDE EXAMPLE
const base = process.env.MICRO_BASE_URL!;const key = process.env.MICRO_API_KEY!;const operationId = "YOUR_SAVED_OPERATION_ID";​const response = await fetch(  base + "/api/live/v1/orders",  {    method: "POST",    redirect: "error",    signal: AbortSignal.timeout(30_000),    headers: {      Authorization: "Bearer " + key,      "Idempotency-Key": operationId,      "Content-Type": "application/json",    },    body: JSON.stringify({      "product_id": "prd_b23a635bc3af7a5ae6b81702",      "input": {        "body": {          "url": "https://example.com",          "limit": 10        }      },      "max_cost_microusd": "10000"    }),  });if (!response.ok) throw new Error(await response.text());const result = await response.json();console.log(result);

Firecrawl website map · $0.01 maximum · check availability

A REAL CATALOG EXAMPLE

Map a website.
Start with one request.

The example uses Firecrawl’s website map tool and its actual input shape. It requests up to 10 URLs from example.com with a $0.01 maximum.

  1. Check the tool’s current availability and price.
  2. Set server-side environment variables.
  3. Save the operation ID before submitting.
  4. Follow the returned order ID to its result.

The published base price is $0.005 per call. Check the current quote before spending; a source definition is not a promise of availability.

Run the step-by-step example

Access with boundaries.

Give each integration a scoped credential. Restrict tools, add optional budgets and revoke access from your workspace.

Production access

One durable order.

Keep the operation identity and exact request. A timeout means inspect the original order, with no replacement purchase.

Handle interruptions

Events you can verify.

Receive signed order notifications. Verify signatures, deduplicate events and retrieve the resource for current state.

Verify a webhook

MCP, WITH THE SAME CONTROLS

Connect your agent.
Keep your workflow.

Use Micro tools in an MCP client through remote HTTP and OAuth. Your connection uses the workspace’s ordinary balance and spending controls.

MCP setup and permissions
CONNECT YOUR AGENTREMOTE MCP
codex mcp add micro --url https://www.trymicro.io/mcp
codex mcp login micro

Run in your terminal, then sign in with Micro.

BEFORE PRODUCTION

A few details to get right.

Keep secrets on your server. Never include a live API key in a browser bundle, public repository or conversation.

Keep money exact. API amounts are strings containing integer microdollars. Use integer or decimal arithmetic.

Keep the original order. Save its ID, show pending states and reconcile unknown outcomes before creating new work.

START WITH THE WORK

Find your next building block.

Explore what a tool can do before adding it to your workflow.

Explore the catalog Understand pricing