Your API can get paid by agents. Today.

One import. Two rails. Agents pay per call in USDC or Lightning — you get a USD balance.

Live now · No card required · 0% platform fee during beta

The Problem

Agents are already calling APIs and already able to pay. Most APIs can't accept it.

Building it yourself means running a Lightning node or a Base wallet, writing 402 challenge/verify logic, handling preimages and EIP-712 signatures, reconciling two ledgers — then doing it all again for the second rail.

Or one line of middleware.

Ten minutes to your first paid call.

01 Install

terminal

npm install payagents

One import, no subpaths.

02 Charge for a route

server.ts

import express from 'express';
import { PayAgents } from 'payagents';

const pa = PayAgents.server({ apiKey: process.env.PAYAGENTS_API_KEY! });
const app = express();

app.post('/tool', pa.charge({ price: '0.002 USD' }).express(), (req, res) => {
  // Runs ONLY after payment is verified.
  // req.payagents = { transactionId, amountUsd, rail, chargeId? }
  res.json({ data: 'premium result' });
});

app.listen(3000);

Fastify adapter included. Framework-agnostic handle() for everything else.

Single-rail providers turn away half the market.

Capability	Single-rail providers	PayAgents
Agent holds USDC	Paid	Paid
Agent holds Lightning	Turned away	Paid
Your setup	One integration	One integration

Pick a single rail and you silently turn away every agent holding the other. You never see those requests — they just don't convert. PayAgents answers both from the same middleware.

Built for high-scale API monetization.

Per-route pricing

Different prices for different endpoints, same server.

Verified before your handler runs

No payment logic in your business code.

Zero custody

You never touch keys, wallets, invoices, or preimages.

Full audit trail

Every transaction logged with proofs and hashes.

Ten minutes to your
first paid call.

Get your API key Book 15 min with the founder