One connection.
Start here.

Buy your first service.

No code required. Your Micro workspace is where you choose a service, pay for usage, and collect the result.

1. 1

   Find the right service.

   Browse the current catalog. Read the tool’s inputs, unit pricing, limits, and data handling. Only currently enabled services can be purchased.

2. 2

   Create your account.

   Sign up for Micro. Follow any account verification steps shown at sign-in. Use your Micro account and balance to access supported services in the browser or through the Micro API.

3. 3

   Add funds to your balance.

   Complete required billing details, then open Balance & billing and continue to Stripe Checkout. Credit becomes spendable after payment is verified. A return-page redirect alone does not confirm payment.

4. 4

   Review, authorize, and run.

   Open the tool and complete its guided fields. Use “Fill example inputs” when available, then review and edit the values. Get an estimate and approve your maximum charge in dollars. Micro reserves that amount before execution.

5. 5

   Collect the result and receipt.

   Follow progress in Activity. Once the order succeeds and settles, expand its Usage details to preview images, video, audio or response data and inspect the exact charge. Download the original for the complete output. Unsupported formats remain download-only. Keep the order ID if you need support.

Map a website with your first request.

Use Firecrawl’s website map tool to discover up to 10 URLs from example.com. This example uses a real catalog product, its required input shape and a $0.01 authorization ceiling.

1const base = process.env.MICRO_BASE_URL!;2const key = process.env.MICRO_API_KEY!;3​4const response = await fetch(5  base + "/api/live/v1/catalog/products/prd_b23a635bc3af7a5ae6b81702",6  {7    redirect: "error",8    signal: AbortSignal.timeout(30_000),9    headers: {10      Authorization: "Bearer " + key,11    },12  }13);14if (!response.ok) throw new Error(await response.text());15const result = await response.json();16console.log(result);

The published base price for this map tool is $0.005 per call. Its input is nested under body: a website url and an optional limit. Other tools have different schemas. Prices may change, so use the current contract and quote.

1const base = process.env.MICRO_BASE_URL!;2const key = process.env.MICRO_API_KEY!;3​4const response = await fetch(5  base + "/api/live/v1/quotes",6  {7    method: "POST",8    redirect: "error",9    signal: AbortSignal.timeout(30_000),10    headers: {11      Authorization: "Bearer " + key,12      "Content-Type": "application/json",13    },14    body: JSON.stringify({15      "product_id": "prd_b23a635bc3af7a5ae6b81702",16      "input": {17        "body": {18          "url": "https://example.com",19          "limit": 1020        }21      },22      "max_cost_microusd": "10000"23    }),24  }25);26if (!response.ok) throw new Error(await response.text());27const result = await response.json();28console.log(result);

1const base = process.env.MICRO_BASE_URL!;2const key = process.env.MICRO_API_KEY!;3const operationId = "YOUR_SAVED_OPERATION_ID";4​5const response = await fetch(6  base + "/api/live/v1/orders",7  {8    method: "POST",9    redirect: "error",10    signal: AbortSignal.timeout(30_000),11    headers: {12      Authorization: "Bearer " + key,13      "Idempotency-Key": operationId,14      "Content-Type": "application/json",15    },16    body: JSON.stringify({17      "product_id": "prd_b23a635bc3af7a5ae6b81702",18      "input": {19        "body": {20          "url": "https://example.com",21          "limit": 1022        }23      },24      "max_cost_microusd": "10000"25    }),26  }27);28if (!response.ok) throw new Error(await response.text());29const result = await response.json();30console.log(result);

Save the returned order ID, then continue with Orders & results below. The accepted maximum is a ceiling; the verified final usage charge can be smaller.

Use an account you already have.

Connect your provider key or authorize a supported account in Connections. Administrators manage credentials; workspace members can use the connected endpoints. Keys are encrypted and never returned to the browser or agent after saving.

1. Choose your provider, review the setup instructions, and save your own key or finish authorization. Select the required provider account or additional credential when prompted.
2. Open a provider endpoint in Explore endpoints and select “Use my provider account.” Complete its guided inputs or load its example, then review and approve the request.
3. For the API, create a Micro credential with “Allow connected-provider requests” selected. Read GET /api/live/v1/connections to find its connection ID and GET /api/live/v1/byok/catalog for endpoint IDs and schemas.
4. Replace YOUR_CONNECTION_ID below. Set your Micro API key and a unique, persisted MICRO_OPERATION_ID in your server environment. Submit once, save the returned byk_ ID, and retrieve it through the ordinary order/result routes.

curl "https://www.trymicro.io/api/live/v1/byok/executions" \
  -H "Authorization: Bearer $MICRO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $MICRO_OPERATION_ID" \
  --data '{
  "endpoint_id": "openrouter.micro.chat",
  "connection_id": "YOUR_CONNECTION_ID",
  "input": {
    "body": {
      "model": "openrouter/free",
      "messages": [
        {
          "role": "user",
          "content": "Explain what an API is in one sentence."
        }
      ],
      "max_tokens": 512,
      "stream": false
    }
  },
  "provider_billing_approved": true
}'

Micro charges $0 for BYOK requests and requires no Micro balance. The provider can charge your own account, including for failed or canceled work. Micro spending budgets do not cap those charges. Set any needed limits at the provider. OpenRouter’s openrouter/free is an example of a provider-selected free model route, subject to its availability and account limits.

Use the same connection from an agent

Reconnect Micro MCP and explicitly allow connected-provider actions. Ask your agent to use list_provider_connections, discover_connected_tools, and get_connected_tool before run_connected_tool. Provider credentials stay on the website; never paste them into agent conversations. Existing API keys and OAuth grants do not gain this permission automatically.

Unknown outcomes keep their original ID and are reconciled without resubmitting. Disconnecting prevents new requests; already submitted work may still finish or incur provider charges. Outputs remain private, with the same 30-day retention and early-deletion controls.

From request to result.

Save the returned order ID. Retrieve it to show progress in your application, with bounded polling and backoff. Do not repeatedly create orders to check for completion.

1const base = process.env.MICRO_BASE_URL!;2const key = process.env.MICRO_API_KEY!;3​4const response = await fetch(5  base + "/api/live/v1/orders/YOUR_SAVED_ORDER_ID",6  {7    redirect: "error",8    signal: AbortSignal.timeout(30_000),9    headers: {10      Authorization: "Bearer " + key,11    },12  }13);14if (!response.ok) throw new Error(await response.text());15const result = await response.json();16console.log(result);

Get the completed output

After success, use GET /api/live/v1/orders/{id}/result with your authorized credential. Output is unavailable until the financial state permits delivery. Pending output returns 409; expired output returns 410.

Default output retention is 30 days. Inspect result_expires_at and download what you need before it expires. A canceled or deleted output does not erase the financial record.

Requesting cancellation

Send POST /api/live/v1/orders/{id}/cancel. Queued work can release its reservation before dispatch. Work already submitted needs a verified supplier outcome; a cancellation request is not proof that execution stopped.

Understand the balance.

Add prepaid usage credit with no Micro deposit surcharge. Usage passes through at the verified provider charge with no additional usage markup. Historical receipts retain any fee actually charged at the time.

Deposits start at $5. Optional automatic deposits can save a card through Stripe and replenish a low balance. You choose the threshold, deposit amount and rolling daily usage-credit cap; Micro adds no deposit surcharge. Turn them off in Balance & billing. Payments already submitted still reconcile.

Promotional credit, including the signup gift and eligible coupon or Checkout discounts, is noncash and nonrefundable. A refund can return only the eligible unused cash-paid portion of a deposit. Micro credit coupons are redeemed in Balance & billing; Stripe discount codes are entered at Checkout.

In Developers, spending limits can apply to the workspace, a member or a credential. Optional daily, weekly, monthly and yearly budgets use UTC and include active holds. Leave a budget blank for no additional cap. Weeks start on Monday. These limits cannot authorize spending beyond the available available balance.

API amounts use decimal strings representing millionths of USD. One dollar is 1000000. For example, "1200" is $0.0012. Use integers or decimal arithmetic; avoid floating-point calculations for money.

An order never charges more than its accepted authorization. Unknown supplier outcomes retain their reservation while recovery proceeds. Eligible unused deposit refunds follow the original funding and refund policy.

Recover the purchase you made.

Send the same Idempotency-Key and identical request body to recover an existing order after a lost response. A changed body with the same key returns 409.

A timeout does not prove the supplier failed. Inspect your saved order ID, or recover it using the original key and request. An unknown state is an operational recovery state, not permission to submit the work again.

Errors include code, message, request_id, and details. Include the request ID in a support case. Never send an API secret or full request content to a public issue tracker.

Handle signed notifications.

Register your public HTTPS endpoint in your workspace’s Webhooks screen. Save the signing secret securely. It is distinct from your API credential.

1. Read the exact raw request body before JSON parsing.
2. Read Micro-Signature in the form t=TIMESTAMP,v1=HEX_SIGNATURE. Rotation can add another v1 signature. Reject timestamps more than five minutes old.
3. Calculate HMAC-SHA256 over timestamp + "." + rawBody using the endpoint secret. Compare using a constant-time function.
4. Deduplicate with Micro-Event-Id. Notifications can repeat or arrive out of order.
5. Retrieve the authenticated resource for its current authoritative state.

Production access.

Production credentials authorize real service purchases. Use read-only discovery and quotes before creating an order.

Local development infrastructure and automated QA accounts are separate from production money. They cannot be upgraded into live balances by changing a browser setting or key prefix. Real funding requires verified Stripe payments, and real fulfillment requires a configured supplier connection.

If this deployment says services are not connected, purchases are unavailable. A missing connection is never replaced with a simulated result.