Use Your Coding Agent

Your coding agent (Claude Code, Cursor, or anything that reads URLs) can integrate m8tes for you. Paste one prompt, and it pulls the full docs corpus and writes the integration against your codebase. This page is about your agent doing the integration work, not the agents m8tes hosts.

The prompt

Copy this into your coding agent, add what you want built, and go:

Text

Credentials

Set the API key as an environment variable. Never paste it into a prompt or commit it:

Terminal

Create or rotate a key with POST /api/v2/token or from the Developer dashboard.

No account yet?

Create one in Python; the key comes back immediately:

Python

Or let the agent sign you up (passwordless HTTP flow)

POST /api/v2/signup needs no auth. Omit password and the agent stays credential-free:

cURL

The response contains a setup-only API key. The activation link is emailed to the person only; it is never in the API response. From there:

Set up now. Use the key as a Bearer token to create agents and start the first run. Unverified accounts get 1 preview run.
Detect the gate. After the preview, runs return 403 with error.details.error_code == "EMAIL_VERIFICATION_REQUIRED". Tell the person to open the activation email; resend it with POST /api/v2/verify/resend.
Hand off. The person clicks the link, sets a password, and activates. At activation the setup-only key is revoked. The person mints their own key from the Developer dashboard or POST /api/v2/token.
Know when. Poll GET /api/v2/verify/status with the setup key: is_verified flips to true. A 401 also means the hand-off happened (the key was revoked).

product picks what to provision: "api" (default, the developer product) or "platform" (the team product, with Company Agent and Day-1 onboarding). "api" accounts start in strict multi-tenant mode; pass "require_end_user_id": false at signup to build single-tenant.

Why the hand-off is secure:

Property	Why it holds
The agent never holds a login	Omit `password` and no credential exists for the agent to keep.
The agent can't activate the account	The activation link is emailed to the person only; it is never in the API response.
The agent hands off cleanly	When the person activates, the agent's setup-only key is revoked. The person mints their own key going forward.
The agent can still start work now	A small preview allowance lets the agent run before the email is verified.

The blocked-run response:

JSON

runs_used counts every run the account made, on any meter: it is the preview trip-wire, not a billing figure. The two allowances below it are separate meters and neither funds the other. balance_micros / balance_usd is the prepaid wallet, which runs carrying user_id spend, and it appears only on accounts the wallet funds. runs_remaining is the platform plan, which your own first-party runs spend — the web app, and API calls with no user_id. A user_id run debits the balance and leaves runs_remaining untouched, so on a new API account (strict multi-tenant by default, so every run carries a user_id) you will see it sitting at the full plan allowance. See Billing & Usage.

Good first asks

"create an agent with a Slack tool and run a task that posts a daily summary"
"stream a run's output into our existing job-status UI"
"subscribe a webhook endpoint to run.completed and run.failed, and verify signatures"

Verify the integration

Run the generated quickstart end to end. A first run completes in under two minutes.
Check run.error_code is empty on success paths, and that failures surface the code.
Confirm end-user isolation: a resource created with one user_id is invisible to another.

Next: Quick Start · Errors · Webhooks