Introduction

AI agents need to pay for things and need their own identity — a wallet, an inbox, a vault, a calendar, a signing key. The internet wasn't built for them. Loomal is.

The two paths

Loomal serves two sides of the same network. Pick the one you're building.

Seller — earn USDC per call

You operate a paid HTTP endpoint or MCP tool. Drop our middleware on a handler, and any paying agent (or human) can call it — the SDK handles the x402 challenge, settles USDC on Base, and returns a signed receipt.

app.get(
  "/search",
  requirePayment({ amount: "0.05" }),
  (req, res) => res.json({ results: [/* ... */] }),
);

→ For Sellers — ship a paid endpoint in 5 minutes.

Identity — equip an agent

You're wiring up an agent. It needs a wallet to pay for tools, plus an inbox, encrypted vault with TOTP, calendar, and a DID for signing. One Loomal Identity bundles all of it behind one API key.

curl -X POST https://api.loomal.ai/v0/agent-signup -d '{}'
# → { "platform_key": "lopk-…", "identity": { "rawKey": "loid-…", ... } }

→ For Agents — agent self-signup, one curl. → For Humans — same thing via the Console.

How the pieces fit

Every API key belongs to a Project (Seller or Identity). Every Project belongs to an Org (your workspace and billing container). That's the whole shape.

Where to go next

• Shipping a paid endpoint? → For Sellers
• Wiring up an agent? → For Agents or For Humans
• Want the deeper model? → Concepts covers payments architecture, scopes, mandates, and the key tiers.