Quick reference: The general aixyz skill lives at skills.sh/agentlyhq/aixyz. Consult it for full CLI flags and advanced topics. This guide focuses on the path that matters most to openclaw users.

1. Runs on the internet at a public URL
2. Accepts work requests from other agents (A2A protocol) and from AI clients like Claude Desktop (MCP protocol)
3. Gets paid per request in crypto via the x402 micropayment protocol
4. Is discoverable on-chain via the ERC-8004 registry

Verify:

```bash
bun --version   # should print 1.3 or higher

Why Bun? The aixyz build pipeline uses Bun's native build API and plugin system — this is a hard architectural requirement, not a preference. The CLI (

@aixyz/cli

) cannot run on Node. Bun also includes a built-in test runner, which means no extra test framework is needed. Curious about the full rationale? Read Why Bun.

1. Push your project to a GitHub repository
2. Go to vercel.com → Add New Project → import your repo
3. Set the Build Command to

   bun run build

   and the Output Directory to

   .vercel/output

4. Add your LLM provider API key (e.g.,

   OPENAI_API_KEY

   ) in the Vercel dashboard under Settings → Environment Variables
5. Click Deploy — Vercel gives you a URL like

   https://my-agent.vercel.app

• AWS — use an Application Load Balancer or API Gateway in front of the process
• GCP — use Cloud Run (zero-config container deploy) or a load balancer
• Azure — use Azure Container Apps or App Service
• DigitalOcean — use App Platform or a Droplet with nginx as a reverse proxy

🔒 Least-privilege rule: When exposing the agent process, only open the port the agent listens on (default

3000

). Do not grant the process broader network, IAM, or filesystem access than it needs to serve HTTP requests.

undefined

• Receive payments from callers of your agent
• Pay gas fees when registering on ERC-8004

use-agently

aixyz erc-8004 register

🔐 Private key security — read this carefully:

• Never share your private key with anyone. Anyone who has it controls your funds.
• Never commit it to git or paste it in public channels (Discord, Slack, GitHub, etc.).
• Write it down offline and store it somewhere safe (e.g., a password manager).
• For a production agent that earns significant income, consider a hardware wallet (Ledger, Trezor).

1. Install MetaMask in your browser
2. Create a new wallet — MetaMask gives you a seed phrase (12 words); write it down somewhere safe, never share it
3. Copy your wallet address (starts with

   0x…

   )

Your wallet address is your "bank account number." You share it publicly. Your private key / seed phrase is your password — never share it, never commit it to code.

1. Create an account on any exchange above (identity verification required)
2. Buy a small amount of the relevant coin (a few dollars is enough for registration)
3. Withdraw to your wallet address
4. Wait for the transaction to confirm (~1–5 minutes)

No crypto yet? You can still build and run your agent locally and on Vercel without registration. Register once you are ready to be publicly discoverable.

accepts

app/agent.ts

import type { Accepts } from "aixyz/accepts";

// Gate the /agent endpoint — callers pay $0.005 per request
export const accepts: Accepts = { scheme: "exact", price: "$0.005" };

aixyz.config.ts

export default {
  name: "my-agent",
  // ...
  x402: {
    payTo: "0xYourWalletAddress", // ← paste your address from Step 4
  },
} satisfies AixyzConfig;

bunx create-aixyz-app my-agent --yes --pay-to 0xYourWalletAddress

Payments flow directly to your wallet — no platform takes a cut.

• bun run dev

  works locally and the agent responds correctly
• Agent is deployed to a public URL (Vercel or similar)
• LLM provider API key (e.g.,

  OPENAI_API_KEY

  ) and any other secrets are set as environment variables on the platform, not committed to your repo

• aixyz.config.ts

  has the correct

  name

  ,

  description

  , and

  payTo

  address
• ERC-8004 registration is complete and the registry shows your agent URL

• accepts

  export is set so your agent earns from requests

Registration is only half the work. Getting on-chain doesn't automatically bring users. You need to actively promote your agent.

• Write a clear, specific

  description

  in

  aixyz.config.ts

  — this appears in the A2A agent card and on-chain registry
• Add an

  app/icon.png

  — a good icon makes your agent stand out in listings
• Post your agent URL and ERC-8004 agent ID in the openclaw community

• Share your

  /.well-known/agent-card.json

  URL — it is the standard entry point for agent-to-agent discovery
• Add your agent to relevant directories and marketplaces (check aixyz.sh for current listings)
• Write a short demo showing what your agent does and how much it costs — post on X/Twitter, Farcaster, or Discord communities

• Too expensive → no callers; too cheap → not worth running
• Start with

  $0.001

  –

  $0.01

  per request and adjust based on demand
• Monitor your wallet — incoming transactions tell you who is using your agent and how often

• Add more tools to make your agent more useful
• Respond to issues and feedback
• Update your on-chain registration if your URL changes:

  aixyz erc-8004 update --help

• aixyz docs — full documentation
• General aixyz skill — CLI reference for advanced usage
• ERC-8004 protocol — on-chain identity deep dive
• x402 payments — payment protocol details
• Examples — working agents to learn from