Quick start

Give your agent managed SMS in minutes.

cxntion bridges two-way SMS conversations between your managed number and your self-hosted agent without taking over the agent itself.

01

Request access

Public beta access is reviewed so each managed SMS number starts with a concrete two-way use case.

Join review queue
02

Create an agent

From the dashboard, create an agent, name it, and keep the agent ID plus API key handy.

Open dashboard
03

Install the CLI

Run the setup wizard, or use init --yes for a droplet, PM2, systemd, or any scripted host.

npx cxntion init
04

Doctor your endpoint

Verify cxntion API auth, tunnel reachability, endpoint auth, model availability, latency, and metadata support before connecting.

npx cxntion doctor
05

Connect your endpoint

Run the bridge wherever Hermes, OpenClaw, or your compatible endpoint already lives.

npx cxntion connect
06

Activate a beta SMS number

After manual review and Pro activation, provision a US SMS number for the agent from the dashboard.

07

Use SMS in production

After manual activation, users text the provisioned number and receive two-way conversational replies from your agent.

Scriptable setup

Same flow, no prompts.

init --yes is for production hosts. It writes local config once; doctor proves the endpoint before connect opens the tunnel.

Hermes

npx cxntion init --yes \
  --key "$CXNTION_API_KEY" \
  --agent "$CXNTION_AGENT_ID" \
  --adapter hermes \
  --target http://localhost:8642/v1/chat/completions \
  --model hermes-agent \
  --api-key-env API_SERVER_KEY
npx cxntion doctor
npx cxntion connect

OpenClaw

npx cxntion init --yes \
  --key "$CXNTION_API_KEY" \
  --agent "$CXNTION_AGENT_ID" \
  --adapter openclaw \
  --target ws://localhost:18789
npx cxntion doctor
npx cxntion connect