Route6 Documentation

Route6 is the network infrastructure layer built for autonomous AI agents. Your organisation gets a dedicated IPv6 /64, and each agent its own public address within it, a DNS hostname, port forwarding, and a private mesh network — all reachable through a built-in MCP server.

⚡

Free tier available. Start with a public IPv6 identity in 60 seconds — no credit card required. Register → (opens in a new tab)

Start here

curl -fsSL https://dl.route6.me/install.sh | sh

That installs r6me, a single binary. Run r6me up and your agent has its own public IPv6 address, an MCP endpoint on localhost:3000, and an egress proxy that sends traffic out from that identity. It runs as a normal user — no root, no kernel modules, no container runtime.

Quick Start →Team Plan →Team & Mesh Tools →Scraper Pipe →

Connection methods

How your agent reaches Route6 is a separate choice from what you pay for. Every method exposes the same 23-tool MCP surface and the same public address space; any plan can use any of them.

	What it is	Choose it when
Binary (recommended)	`r6me`, one static executable, run as a normal user	Almost always. It is the smallest thing that works.
Container	The same binary in a minimal image	Your environment requires a container, or your services already live in one
Serverless	No client at all — MCP straight at `gw.route6.me` with a Bearer token	You cannot run a long-lived process: Lambda, Cloud Run, an edge worker, a hosted agent platform

The trade-off is what your agent can receive. The binary and the container carry inbound traffic and the private mesh; serverless is outbound MCP calls only. See each page for the exact surface.

What Route6 provides

Every plan — Free included — gets all 23 MCP tools, a public IPv6 address per agent, a *.on.route6.me hostname, port forwarding, an IPv4 webhook URL and a private mesh between its agents. Plans differ in capacity: how many agents, metered or unmetered egress, scraper credits. A few capabilities need a paid plan — choosing your own hostname, buying scraper credits, the Static IPv4 add-on and direct outbound SMTP — and the tool tells you so when you call it.

The full, current comparison is generated from the enforcing code at route6.me/pricing (opens in a new tab).

How it works

Sign up at route6.me (opens in a new tab) — a free agent is provisioned after email verification.
Copy your API key from the dashboard. It starts with sk_a6_.

Install and connect:

curl -fsSL https://dl.route6.me/install.sh | sh
mkdir -p ~/.r6me && chmod 700 ~/.r6me
echo 'api_key = "sk_a6_your_key_here"' > ~/.r6me/config.toml && chmod 600 ~/.r6me/config.toml
r6me up

Point your AI tool at the MCP server on http://localhost:3000/mcp — see MCP Integration.

Architecture summary

  Your machine                        Route6 edge
  ┌──────────────────┐                ┌────────────────────────┐
  │  r6me (one binary)│                │                        │
  │  ┌─────────────┐ │   HTTPS mux    │  BGP-announced         │
  │  │ MCP :3000   │◄├────────────────┤  IPv6 /64 routed       │
  │  │ egress :1080│ │   (identity)   │  to your agent         │
  │  │ status :3001│ │                │                        │
  │  └─────────────┘ │   WireGuard    │  DNS64 / NAT64         │
  │   userspace WG   │◄───────────────┤  for IPv4 access       │
  │   (mesh only)    │   (mesh)       │                        │
  └──────────────────┘                └────────────────────────┘

Outbound traffic and inbound forwards ride the HTTPS connection and are terminated at our edge, so your machine never binds a public address. The WireGuard overlay carries only private mesh traffic between your own agents.

Quick Start