What exact payment rails does PayAgents support?

PayAgents natively supports L402 utilizing SATs (Bitcoin Lightning) and x402 utilizing USDC on the Base chain. Future roadmaps include other EVM chains, Taproot stablecoins, and traditional fiat card/ACH rails.

Do I need to manage multiple crypto assets and wallets?

No. PayAgents provides a unified wallet framework that abstracts cryptocurrency complexities, maintaining a clean USD balance sheet while automatically routing between USDC (Base) and Lightning SATs.

What is the platform pricing structure?

During the private beta phase, platform pricing is completely zero (0%). A minor developer fee may be introduced later to support persistent liquidity networks.

How do Policy Engines protect against spend chaos and hallucinations?

PayAgents provides granular policy controls including hard spend caps per transaction, day, and 30 days, domain allowlists/denylists, and manual approval triggers for high-dollar requests to prevent runaway LLM loop spending.

How does Model Context Protocol (MCP) server monetization work?

With a single line of server-side middleware (payagents-mcp), you can add micro-fees (e.g., $0.002 per call) to specialized tools. PayAgents intercepts incoming agent requests, verifies L402/x402 settlement, and credits your balance or non-custodial wallet instantly.

Does PayAgents offer a non-custodial option?

Yes. When receiving payments for your APIs or MCP servers, you can configure your personal Base EVM address (USDC via x402) and Lightning address (via L402). All incoming payments from AI agents settle directly peer-to-peer into your wallet with zero platform custody.

One SDK.
Any agent.
Any rail.

Give your AI Agents power to transact.
One integration - your agent can pay and be paid across Lightning L402, x402, and more. Monetize your MCP server in one line.

Try the beta — free Book 15 min with the founder

Live now · No card required · Talk to the person who built it.

quickstart.ts

import { PayAgents } from 'payagents';

const client = new PayAgents({ apiKey });

// pay any agent-gated endpoint
await client.pay('api.llm.io/infer', {
  maxAmount: '0.001 USD',
  payload: { prompt: 'summarize' },
});

// ↳ rail auto-selected · Lightning

The API

The Simplest Payment API.

Many use cases. One API key. Routing, retries, rail selection, compliance — all handled server-side.

YOU RECEIVE

Gate endpoints and MCP tools behind automated micro-payments.

receiving-agent.ts

import { PayAgents } from 'payagents';

const server = PayAgents.server({ apiKey });

// charge for any endpoint
server.charge('/infer', {
  price: '0.001 USD',
  handler: (req) => runModel(req),
});

402

YOU PAY

Give agents policy-controlled wallets to unlock paid APIs instantly.

paying-agent.ts

import { PayAgents } from 'payagents';

const client = new PayAgents({ apiKey });

// pay any agent-gated endpoint
await client.pay('api.llm.io/infer', {
  maxAmount: '0.001 USD',
  payload: { prompt: 'summarize' },
});

Monetize Your MCP Server Infrastructure.

You don't know who will call your MCP server — or which payment rail they use. PayAgents handles all of it. One line of middleware, any agent can pay you.

YOU RECEIVE

Monetize tools on Claude Desktop, Cursor, and custom MCP servers.

mcp-server.ts

import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import { mcpCharge } from 'payagents-mcp';
import { z } from 'zod';

const server = new McpServer({ name: 'tools', version: '1.0.0' });

// Gate any MCP tool behind micro-payments
server.tool('web_search',
  'Search live web',
  { query: z.string(), payment_proof: z.string().optional() },
  mcpCharge({ price: '0.002 USD' }, async ({ query }) => {
    return { content: [{ type: 'text', text: await search(query) }] };
  })
);

402

YOU PAY

Give Claude Desktop & Cursor an autonomous wallet via MCP config.

claude_desktop_config.json

{
  "mcpServers": {
    "payagents": {
      "command": "npx",
      "args": ["-y", "payagents-mcp"],
      "env": {
        "PAYAGENTS_API_KEY": "pa_live_..."
      }
    }
  }
}

Accept any rail

Lightning, x402, or both — you decide in your dashboard.

Per-tool pricing

Charge different prices for different tools in the same server.

Instant settlement

Funds land directly in your wallet or accumulate in your USD balance.

Direct or Managed

Zero platform custody direct to your Base/Lightning wallet, or managed USD ledger.

Why PayAgents

Give your agent the ability to transact.

Spend controls, multi-rail routing, liquidity, and a full audit trail — added to any agent or MCP server in one line.

Your Agent

Active Engine

PayAgents Engine Policy · Routing · Settlement

Lightning

x402

Fiat (soon)

Capability	The hard part	Recommended With PayAgents
Liquidity	You fund + rebalance sats & USDC.	One USD balance. We manage rails.
Failover	A retry loop you write and maintain.	Automatic cross-rail failover.
Correctness	Payment edge cases: timeouts, double-pays.	Two-phase settlement, fail-safe.
Control	Spend limits are another thing you build.	Policy engine: limits, allowlists, approvals.
Audit	Logs you stitch together yourself.	Every transaction logged with proofs & hashes.

Payment rails

Automated Lightning x402 Payment Rail Routing.

Whether you're paying an agent or receiving from one — PayAgents routes to the cheapest, fastest rail both sides support. MCP servers can accept any rail simultaneously.

Lightning Network

Sub-cent micropayments settled in milliseconds. Bitcoin-native, permissionless, censorship-resistant. Ideal for high-frequency agent calls.

L402 SATs instant

x402 / Base

Stablecoin payments on the Base chain via the x402 standard. Ideal for low-fee dollar-denominated agent tools. Built for machine-understandable 402 integration.

x402 USDC Base Chain

EVM, Taproot & Fiat

Expanding to more EVM networks for x402, native stablecoin configurations over Bitcoin Lightning via Taproot, and traditional fiat card rails.

Taproot Asset Fiat Rails Roadmap

How it works

Four steps. Done.

Create a PayAgents account and grab your API key from the dashboard. Takes 30 seconds.

Install

npm install payagents. Plug in your API key. That's the entire setup.

Call

Your agent calls client.pay(). PayAgents detects the protocol and routes to the best rail automatically.

Done

Payment settles, your agent gets its response. Every transaction logged in your dashboard.

FAQ

Frequently Asked Questions

Everything you need to know about giving transactional abilities to your AI agents.

Right now, we natively support **L402 utilizing SATs (Bitcoin Lightning)** and **X402 utilizing USDC on the Base chain**.

Our infrastructure roadmap includes adding other EVM chains for X402 support, native stablecoins directly on Bitcoin Lightning via Taproot, and traditional fiat card/ACH rails in upcoming rollout phases.

No. We provide a **unified wallet framework** that abstracts away all cryptocurrency complexities. Your account maintains a clean **USD balance** sheet.

In the background, our core engine programmatically handles all liquidity management, swapping, and value routing between USDC (Base) and Lightning SATs. You simply configure the exact target USD amounts without ever worrying about raw token management, gas limits, or underlying crypto rails.

For now, during our private beta phase, platform pricing is completely **zero (0%)**.

Later on, as we scale global machine routing volumes, we may introduce a minor developer platform fee of **1 percent** on each completed transaction link to support persistent liquidity networks.

One of the largest risks in multi-agent environments is an LLM hallucination causing a recursive calling loop that rapidly drains corporate capital. PayAgents solves this with rigid granular policy configurations.

From your control panel, you can enforce hard caps on a **per-transaction, per-day, and per-30-days** basis. Additionally, you can construct clean domain track-record guardrails specifying exact **allowed and disallowed destination domain lists** and establish manual approval triggers that intercept and stall any call exceeding your specific dollar thresholds.

By importing our single line of server-side middleware, you can add explicit micro-fees (e.g., $0.002 per call) to specific specialized tools or search utilities in your server. When external agents call your tool, PayAgents intercepts, checks if they support L402 or x402, authenticates the incoming settlement rail, verifies fulfillment proofs, and drops the payment into your designated wallet or dashboard balance instantly.

Yes! When receiving payments for your APIs or MCP servers, you can configure your personal Base EVM address (for USDC via x402) and/or your Lightning address (via L402) in Settings. All incoming payments from AI agents settle directly peer-to-peer into your personal wallet with zero platform custody.

For Outbound Agent Spending: Autonomous AI agents cannot prompt a human for a wallet signature on every $0.001 micropayment. You pre-fund a dedicated agent budget balance in your dashboard, protected by hard spending caps, domain allowlists, and human approval thresholds, allowing your agents to pay for tools 24/7 autonomously without exposing your primary treasury.

Built for what's
coming next.

Agents paying agents. MCP servers earning revenue. It's live now — get your API key and start charging, or talk it through with the founder first.