Accept payments from multiple AI agents. One catalog. Every major wallet.

1. 01
   Freelancer

   An agent books your hour

   A research agent needs a 60-minute audit. It reads /a/@you, pays the listed price in USDC, and the intent shows up beside your human clients.

   No DM. No invoice chase. Session is paid before you open Zoom.

2. 02
   Specialist

   Packages sell without a thread

   Your critique, retainer or delivery package is already on the service page. Collect makes it machine-readable—agents buy the SKU, humans still use /s/@you.

   One catalog. Two kinds of buyers. Same balance.

3. 03
   API / product

   Gate a route, get paid per call

   Wrap an endpoint with express-vybe-402. The agent hits HTTP 402, settles on Base, retries, and your webhook fires when it’s paid.

   Cloudflare gives them a wallet to spend. You collect on the response.

4. 04
   Studio / agency

   Brand catalog, agent traffic

   Publish offerings under one @brand. Ops agents and human clients book from the same list—retainers, audits, impl sprints—without a second billing stack.

   Agent revenue lands next to client revenue. Cash out the same way.

1. 01

   What you’re building

   Pay-per-call (or pay-per-route) access for agents and programmatic clients—not a card checkout page for shoppers.

2. 02

   What you install

   npm i express-vybe-402 on your API server. Point it at your Vybe @username and an offering id from your Collect catalog.

3. 03

   What callers experience

   First hit → HTTP 402 with payment details. They settle USDC or USDT on Base, Ethereum, or BNB (x402 or tx hash). Retry with X-Vybe-Public-Id → your code runs.

4. 04

   Where money lands

   Your Vybe balance—same as human payment requests. Optional payment.paid webhook for fulfillment.

• Not Stripe Checkout / Elements for a marketing site
• Not a hosted pay button you drop into HTML
• Not fiat card acquiring—settlement is USDC & USDT on Base, Ethereum, and BNB

Layer 1 — what the agent sees

Protocol vybe-agent-collect v0.1: HTTP 402 Payment Required (x402-shaped), settle with a txHash, or poll until paid. Human fallback lives at /r/….

BASE=https://vybe.finance/api/agent/collect/alex

# 1. Discover offerings
curl $BASE

# 2. Start checkout (returns HTTP 402)
curl -X POST $BASE/svc_9fQ2Kd

# 3a. x402 clients retry with PAYMENT-SIGNATURE (facilitator settles)
# curl -X POST $BASE/svc_9fQ2Kd -H "PAYMENT-SIGNATURE: <base64>"

# 3b. Or after a USDC/USDT transfer on Base, Ethereum, or BNB — settle with txHash
curl -X POST $BASE/svc_9fQ2Kd/status \
  -H 'Content-Type: application/json' \
  -d '{"publicId":"Vh3xR2mQ","txHash":"0x…","chain":"base"}'

# 4. Or poll until paid
curl "$BASE/svc_9fQ2Kd/status?publicId=Vh3xR2mQ"

HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: <base64 x402 v2>

{
  "protocol": "vybe-agent-collect",
  "version": "0.1",
  "x402Version": 1,
  "accepts": [
    { "network": "eip155:8453", "asset": "USDC on Base", "…" },
    { "network": "eip155:1", "asset": "USDC on Ethereum", "…" },
    { "network": "eip155:56", "asset": "USDT on BNB", "…" }
  ],
  "vybe": {
    "publicId": "Vh3xR2mQ",
    "requestUrl": "https://vybe.finance/r/Vh3xR2mQ",
    "statusUrl": "https://vybe.finance/api/agent/…/status",
    "expiresAt": "2026-08-08T18:04:11.000Z"
  }
}

Layer 2 — what your server does

One Bearer key manages the same catalog your service page shows. When an agent settles, we verify the transfer on Base and POST you a signed event—so your fulfilment runs without anyone watching a dashboard.

# Create / rotate a server key
POST /api/collect/v1/credentials

# Upsert offerings + enable Collect
PUT /api/collect/v1/offerings
Authorization: Bearer vybe_col_…

# Register your webhook
PUT /api/collect/v1/webhook
{ "url": "https://you.com/hooks/vybe" }

POST https://you.com/hooks/vybe
X-Vybe-Signature: sha256=…

{
  "type": "payment.paid",
  "publicId": "Vh3xR2mQ",
  "offeringId": "svc_9fQ2Kd",
  "amount": "150.00",
  "token": "usdc",
  "settlementTxHash": "0x…"
}

Layer 3 — gate your own endpoints

express-vybe-402 sits on the routes you choose. Unpaid requests never reach your handler: the middleware returns 402 with a Collect intent, then calls next() only after status is paid.

import express from "express";
import { requireVybePayment } from "express-vybe-402";

const app = express();

// Agents get HTTP 402 until they pay for this route.
app.get(
  "/v1/insights",
  requireVybePayment({
    username: "alex",
    offeringId: "svc_9fQ2Kd",
  }),
  (req, res) => res.json({ data: buildInsights() }),
);

// The agent retries with the settled intent:
//   X-Vybe-Public-Id: Vh3xR2mQ

• Catalog: GET /api/agent/collect/{username}
• Intent: POST …/{offeringId} → HTTP 402 + PAYMENT-REQUIRED
• Settle: PAYMENT-SIGNATURE retry, or POST …/status with txHash
• Individuals never need keys—toggle Collect in Settings → Service page