Agent OS

Agents that pay on your Vybe ledger.

Vybe Agent OS: policy-bound payments for B2C and B2B—HTTP 402 where crypto unlocks APIs, Stripe ACP where merchants speak that language. Same balance humans already use.

Join the waitlistOpen my balance
HTTP 402 Session keys + caps Same Vybe ledger
9:41● ●
AgenticKeys with caps · agents ask
Agent wants to pay$0.05POST /v1/enrichUnder $25 session capReview · Approve or Decline ›
$2,840.50
@alex
SendRequestInviteScan
Add money
Recent callsAll
  • EPOST /v1/enrichPaid · 0.8s$0.05
  • IGET /v1/insightsPaid · just now$0.12
  • KSession keyCap live · domain lockedActive
Payment requiredSettled
Why cardless

Agents don’t swipe cards. They call APIs.

Legacy card rails assume a human in a browser. Autonomous agents need programmable money: tiny amounts, cryptographic auth, and hard spend limits—not a virtual Visa stuck behind CAPTCHA.

Built for micro-payments

Card swipe fees (~$0.15–$0.30) kill sub-cent API calls. Settle in USDC on Base where small amounts actually make sense.

HTTP 402, not checkout forms

Gate endpoints with Payment Required. Agents handshake cryptographically—no CAPTCHA, no 3DS, no browser card form.

Session keys with hard limits

Users delegate spend to agents with hard caps, expiry, and domain locks. Hallucination loops don’t drain the wallet.

Same Vybe ledger

Humans and agents share one balance and identity. Crypto, 402, or ACP—the router picks the rail; policy stays in Vybe.

Before / after

Same balance. Rails agents can actually use.

Cards

Fixed card swipe fees

Vybe

Sub-cent USDC settlements

Cards

3DS / CAPTCHA / anti-bot

Vybe

API + HTTP 402 handshake

Cards

16-digit numbers in prompts

Vybe

Scoped session keys + revoke

Cards

Merchant card acquiring

Vybe

Middleware + SDK on your API

What’s coming

Middleware, SDK, policies—on the wallet you already know.

Human Vybe ships today (one balance, @username, payment requests, bank funding where live). Agent OS is next: policy engine, 402, ACP adapters—grant-ready demos first, then public packages.

express-vybe-402

Middleware to require payment before your route runs.

@vybe/agent-sdk

TypeScript (then Python) helpers for agents that pay as they go.

Policy engine

Hard caps, velocity limits, allowlists—enforced before settlement.

Exampleexpress-vybe-402
import { vybe402 } from "express-vybe-402";

app.get(
  "/v1/enrich",
  vybe402({ priceUsd: "0.002", token: "usdc" }),
  async (req, res) => {
    res.json({ ok: true, data: await enrich(req.query) });
  },
);
Live · Golive 2

Vybe Pay MCP

For humans: your AI asks, you Approve. For builders: paste a VAPT into Cursor or Claude. Agents call pay_offering under your caps — you Approve in Vybe (Monzo-style). No silent unlimited spend.

pay_offering

Start Collect pay → awaiting your Approve.

get_limits

Per-tx max, daily cap, allowlist, expiry.

get_spend_balance

Policy headroom used in the last 24h.

list_recent_pays

Pending and paid agent spends for this VAPT.

Cursor · mcp.json/api/mcp/pay
{
  "mcpServers": {
    "vybe-pay": {
      "url": "https://vybe.finance/api/mcp/pay",
      "headers": {
        "Authorization": "Bearer vapt_YOUR_TOKEN"
      }
    }
  }
}

Spec in repo: docs/VAPT.md · docs/GOLIVE.md · endpoint GET/POST /api/mcp/pay

Early access

Get the SDK when it ships.

Join the list for express-vybe-402 and @vybe/agent-sdk. We’ll reach out for design partners building agent tools, API metering, and autonomous workflows.

Also human

Need the human balance first?

Freelancers and teams use Vybe today—one balance, pay by @username, request fixed amounts, fund via bank where available.

Open my balanceBack to home