Maritimemaritime
Dashboard

OpenClaw Identity Guide

OpenClaw with a real phone number and email address.

Overview

OpenClaw Identity is the OpenClaw runtime plus a per-agent Inkbox identity: a real email address, an SMS-capable phone number, and a public tunnel hostname. Inbound email and SMS are bridged into the agent automatically.

Docker Image

Image: ghcr.io/mariagorskikh/openclaw-identity:2026.6.4 — OpenClaw plus the Inkbox bridge, pre-baked

What Gets Provisioned

At create time Maritime calls Inkbox's POST /api/v1/identities (documented in the Inkbox API docs) to atomically provision:

  • An identity with handle maritime-<agent-id-prefix>
  • A mailbox at <handle>@inkboxmail.com
  • A public tunnel at <handle>.inkboxwire.com
  • A local US phone number (sends and receives SMS, voice auto-reject)
  • A scoped API key bound to that identity only

How It Works

The container starts a Node bridge (inkbox_bridge.mjs) that opens an outbound HTTP/2 tunnel and forwards POST /webhooks/email and POST /webhooks/textinto openclaw agent --message .... Replies go back through the Inkbox SDK.

# Env vars set on the container:
INKBOX_API_KEY=<scoped key, encrypted>
INKBOX_IDENTITY_ID=<uuid>
INKBOX_AGENT_HANDLE=maritime-<prefix>
INKBOX_EMAIL=<handle>@inkboxmail.com
INKBOX_PHONE_NUMBER=+1...
INKBOX_PHONE_NUMBER_ID=<uuid>
INKBOX_TUNNEL_HOST=<handle>.inkboxwire.com

SMS Warm-up

New local numbers go through 10DLC campaign propagation, which takes ~10–15 minutes. During that window inbound SMS works immediately, but outbound returns 409 sender_sms_pending. The agent page surfaces this as "warming up" rather than an error. Recipients must reply START to any number in the org before they can receive outbound SMS. Phone-number types, opt-in rules, and per-number sending limits are Inkbox platform behavior — the Inkbox docs are the authoritative reference.

Deploy

Select Template → OpenClaw Identity in the Create Agent modal. Identity provisioning happens during create, so the agent already has its phone and email by the time the container boots.

Upstream links & resources

  • inkbox.ai — the identity provider behind this template: what an agent identity is (email + phone + tunnel) and how it works.
  • Inkbox documentation — the full API reference: identities, mailboxes, texting (phone-number types, 10DLC warm-up, opt-in rules), tunnels, and webhooks. Read this to understand what your agent's identity can and can't do.
  • inkbox-ai/inkbox — the official Python SDK, skills, and examples. The in-container bridge uses this SDK to send email and SMS replies.
  • Inkbox console — Inkbox's own dashboard for numbers and mailboxes. Maritime provisions and manages your agent's identity for you, so you only need this if you also use Inkbox directly.
  • OpenClaw documentation — the underlying agent runtime this template runs: configuration, skills, and gateway behavior. See also the openclaw/openclaw source repo and our OpenClaw guide.