Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Agentic Commerce

Doma exposes its commerce primitives (buy, sell, register, configure) as AI-native records that any LLM agent can discover and execute. The discovery layer is AgentRoot, an open DNS-based protocol; the execution layer is the Doma CLI. This section covers how the stack fits together.

The three-step model

Three-step model: install Doma skills via AgentRoot once, prompt the agent in English for every operation, the skill drives the Doma CLI and wallet automatically.

AgentRoot is a general-purpose discovery protocol; any domain can publish capabilities through it. This section walks through the Doma case: the user installs Doma's skills via AgentRoot once, then talks to the agent in English to run operations on Doma. The same three steps apply to any AgentRoot-published capability at any domain.

  1. Install Doma's skills via AgentRoot (one time). The user asks the agent to install the skills published at doma.xyz: e.g. "Use AgentRoot to install the trade-tokens skill from doma.xyz", or "install all doma.xyz skills". The agent's AgentRoot MCP resolves doma.xyz, fetches the matching SKILL.md files, and drops them into the agent's skills folder. From this point on, the skills are part of the agent's runtime context (portable across Claude Code, Cursor, Codex CLI, Gemini, OpenCode).

  2. Prompt the agent in plain English (every operation). With the skills installed, prompts like "buy 10 USDC of <token> on Doma testnet" or "register mydomain.io via MPP" match against the installed skills' trigger phrases. The user does not pick which skill runs; the agent matches the prompt.

  3. The skill drives the Doma CLI and the wallet. The matched skill orchestrates everything below the prompt: it calls Doma CLI commands, triggers the agentic wallet browser sign-in the first time a signature is needed, surfaces confirmations, and reports results. The user doesn't type any doma <command> lines.

Protocol stack

Protocol stack with two phases. ONE-TIME SETUP via AgentRoot: user prompt resolves _agentroot.doma.xyz through DNS, fetches the zone file, installs SKILL.md files into the agent's skills folder. EVERY OPERATION via the installed skill: user prompt is matched to an installed skill, the skill orchestrates Doma CLI commands, the wallet signs (agentic wallet or local private key), and on-chain settlement happens on Doma, Ethereum, or Base.

Prerequisites

You configure the toolchain once. After that, you talk to your agent in plain English; the skill drives the CLI, the wallet, and the on-chain calls. You don't have to remember any doma … commands.

  • Node.js ≥ 20. Required for both agent-root (the AgentRoot CLI) and @doma-protocol/cli.

  • An AI agent that can load SKILL.md or MCP tools. Claude Code, Claude Desktop, Cursor, Codex CLI, Gemini CLI, or OpenCode.

  • Install the Doma CLI: npm install -g @doma-protocol/cli (one time).

  • Pick a wallet path:

    • Agentic wallet (recommended). Nothing to configure up front. The first time a skill needs a signature, it triggers doma auth login for you. You click Authorize in the resulting browser tab once, and Privy is your signer from then on. No key on your machine. Spend cap enforced server-side. Revocable any time.

    • Local private key. export DOMA_PRIVATE_KEY=0x… once. The skill uses that key for every signature. Faster setup, no browser dance, but the key sits on disk and the wallet has unbounded spend authority. Use a dedicated test wallet.

The doma <command> lines that appear in the Doma CLI reference are what the skill runs on your behalf. As a user you don't need to memorize or type them. They're documented so you understand what's happening under the hood and so you can use the CLI directly if you want.

Where to go next

PreviousFor RegistrarsNextAgentRoot

Last updated