Root My Android for AI agents

Why Root My Android is agent-friendly

• Accounts without identity. Accounts are Mullvad-style 16-digit numbers — there is no email, password, phone, or KYC step anywhere in the flow. Those identity gates are exactly where agents usually get stuck; here they do not exist. An agent can create an account for its user and act on it with just the number — revocable, scoped sessions for AI features are on the roadmap.
• Public by design. No API keys, no OAuth apps, no approval waitlists for the API itself — the exposed services are public, and an account number is the only credential where one is needed.
• MCP-native. One well-known URL speaks the Model Context Protocol; any MCP-capable client (Claude, Cursor, or a custom agent) connects by adding the server to its config.
• Money rails agents can actually use. The card rail returns a hosted invoice URL to hand to the user, and the crypto rail settles without a bank account — 15% off listed prices, enforced server-side.
• Self-healing payments. Payment status is reconciled authoritatively on the server, so a missed webhook never strands a user's credit.

Connect your agent (MCP server)

The endpoint is POST https://rootmyandroid.com/mcp(a plain GET returns the human-readable catalog). Add the server to any MCP-capable client:

{
  "mcpServers": {
    "rootmyandroid": {
      "type": "http",
      "url": "https://rootmyandroid.com/mcp"
    }
  }
}

Or drive it by hand — every message is one POST with a JSON-RPC 2.0 body, and responses are single application/jsondocuments: no SSE streams, no session headers, no batching.

curl -sS https://rootmyandroid.com/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
        "protocolVersion":"2025-06-18","capabilities":{},
        "clientInfo":{"name":"my-agent","version":"1.0.0"}}}'

Protocol facts: the server is rootmyandroid-mcpv0.1.0; protocol versions 2025-06-18, 2025-03-26, and 2024-11-05 are negotiated on initialize; the transport is stateless — no Mcp-Session-Id is issued; capabilities are tools only (no resources, no prompts). The/mcp pageitself is the always-current reference — its tools table is generated from the same catalog as tools/list.

What agents can do

14 tools at the time of writing (November 2026). This is a capability map — the exact, machine-generated reference lives at/mcp.

• Accounts & entitlements:create_account, get_account,get_entitlements, and verify_feature — the gate every tier feature checks: is feature X unlocked for this account right now?
• Plans & checkout:list_subscription_plans (flat prepaid Guardian Angel tiers with full-fiat and 15%-discounted crypto prices),create_card_checkout (hosted invoice URL),create_crypto_checkout (whitelabel deposit address, amount, and currency), and get_payment_status.
• Vouchers: redeem_voucher — a single-use code that credits its days of Guardian Angel PRO to an account.
• Human support:open_support_conversation(realtime = anonymous live chat;message = asynchronous, requires an email),send_support_message, andpoll_support_messages. Conversations opened via MCP share one 5/day quota, because all MCP calls originate from the same Worker.
• Diagnostics & discovery:get_network_identity (your egress IP, user agent, ASN, TLS version, and geolocation echoed from Cloudflare edge metadata — nothing is stored) and get_api_index(every public REST endpoint).

The REST API behind it

Every MCP tool is a thin proxy of the public REST API atrootmyandroid.com/v1, which owns all validation and business logic. Device-facing endpoints (encrypted backups, Guardian Angel pairing, audit snapshots) remain REST-only for now — they need an on-device context an agent cannot fabricate.

What agents sell or manage: Guardian Angel monitoring for up to 5 devices per account — Lite at $5 / 30 days, Pro at $15 / 30 days; subscribers can switch between Lite and Pro anytime, and crypto payments save 15%. Full details on ourpricing page.