Use your coding agent

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

curl -X POST https://api.m8tes.ai/api/v2/signup \
  -H "Content-Type: application/json" \
  -d '{"email": "alex@acme.com", "first_name": "alex"}'

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:

1. Connect a model provider (local) or use the $1 test lane / top up (prod embeds), then set up. For a cold hello-world, use the API starter credit on the pinned test model (see Quick start). For personal development, connect a matching model subscription and run without user_id. For production embeds, top up after the starter pin for the full catalog. Then use the key as a Bearer token to create agents and start runs. Unverified accounts may complete up to 25 runs before email verification is required.
2. Detect the gate. After that verification threshold, 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.
3. 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.
4. 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 Lead mate and Day-1 onboarding). "api" accounts start in strict multi-tenant mode; pass "require_end_user_id": false at signup for personal development only. This setting persists account-wide. For customer-facing apps, keep strict mode on and pass user_id.

Run an agent with none of our branding

An agent you embed in your product should sound like your product. By default an agent knows it runs on m8tes: it calls itself a mate, can describe what m8tes does, and knows our pricing. That is right for a team using m8tes directly and wrong for an agent your customers talk to.

Set prompt_profile to "bare" and none of that reaches the agent:

agent = client.agents.create(
    name="Acme Support",
    instructions="You are Acme Support. Answer billing questions for Acme customers.",
    prompt_profile="bare",
    user_id="cust_42",
)

bare removes branding, not ability. Permissions, approvals, memory, files, integrations and your own Agent Skills all work exactly the same.

Switch an existing agent any time with client.agents.update(id, prompt_profile="bare"); it takes effect on that agent's next run.

Turn off any built-in tool

Every agent gets built-in tools (memory, task history, issue reporter, owner-notify email, desktop). Some are wrong for embeds: report_issue files feedback with us, and notify emails the account owner, not your end user. Name them in disabled_builtin_tools to unmount:

agent = client.agents.create(
    name="Acme Support",
    prompt_profile="bare",
    disabled_builtin_tools=["feedback", "notify", "computer_use"],
    user_id="cust_42",
)

Valid names: GET /api/v2/built-in-tools. Pass teammate_id to see what a run will actually mount after your disable list. Unknown names are rejected, so a typo cannot leave a tool on.

for t in client.built_in_tools.list(agent_id=agent.id).data:
    print(t.name, t.enabled)

See exactly what we inject

Returns the real prompt the agent will run, rendered by the same code that runs it:

sp = client.agents.system_prompt(agent.id, user_id="cust_42")
print(sp.prompt_profile, sp.characters)
assert "m8tes" not in sp.system_prompt.replace("/home/daytona/m8tes-files/", "")

One deliberate exception: /home/daytona/m8tes-files/ is the real sandbox directory your agent writes to when it shares a file, so that path survives in bare. It is a filesystem path the agent uses, never something it is told to say.

Per-run context (memories, documents, connected tools, the triggering channel) is resolved when a run starts and is not included in this response.

Why the hand-off is secure:

The blocked-run response:

{
  "error": {
    "type": "permission_error",
    "code": 403,
    "message": "Verify your email to keep running. Check your inbox for the activation link (resend: POST /api/v2/verify/resend).",
    "request_id": "req_...",
    "doc_url": "https://www.m8tes.ai/docs/api-errors#error-types",
    "details": {
      "error_code": "EMAIL_VERIFICATION_REQUIRED",
      "runs_used": 25,
      "verification_threshold": 25,
      "runs_remaining": 50,
      "balance_micros": 0,
      "balance_usd": "0.0000",
      "topup_url": "/billing/api"
    }
  }
}

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 pays for the other.

• balance_micros / balance_usd: the prepaid wallet (runs with user_id). Appears only on accounts with a prepaid balance.
• runs_remaining: the platform plan (your own first-party runs: web app, and API calls with no user_id).

A user_id run debits the balance and leaves runs_remaining untouched. On a new API account (strict multi-tenant by default), you will see runs_remaining sitting at the full plan allowance. See Billing & usage.