Menu

Explorer & Settings

Tempo Explorer Submit Project
Alternatives · Chargebee

AI-Native Alternatives to Chargebee for Agent Payments

Subscription billing assumes plans, seats and invoices — agent revenue is metered per call and settled instantly.

Why Chargebee doesn\u2019t fit agent payments

Chargebee is a recurring-billing platform: plans, seats, invoices, dunning, revenue recognition — the machinery of human SaaS subscriptions. It is very good at that, and entirely mismatched to agent customers. An agent does not sign up for a $49/month tier; it makes 300 calls this hour and none tomorrow. Monthly plans, proration and invoice cycles add friction and cost to a workload that should just be metered per request and paid on the spot.

Agent-native monetization is usage-based by default: price each request or tool call, meter it in real time, and settle in the same HTTP exchange. There is no plan to choose and no invoice to send — the payment rides inside the API call. The open-source projects below provide the metering, paywall and settlement pieces to do exactly that.

What to look for instead

  • True per-request / per-token metering, not monthly plans
  • No signup or plan selection — access granted on payment
  • Real-time settlement inside the API call, not invoice cycles
  • Sub-cent overhead so per-call charging is profitable

The open-source alternatives

Top 12 of 1.3k tracked projects, sorted by GitHub stars. Each is open source and can be self-hosted.

Your AI trading terminal assistant for US stocks, commodities, forex, and crypto.

⭐ 12.6kGo

The agent-native LLM router for autonomous agents. 55+ models (8 free), <1ms local routing, USDC payments on Base & Solana via x402.

⭐ 6.7kTypeScript

A payments protocol for the internet. Built on HTTP.

⭐ 6.4kTypeScript

A local-first AI agent with persistent memory, emotional intelligence, and a peer-to-peer skills economy.

⭐ 2.4kTypeScript

The living ecosystem where AI agents complete tasks through workflow loops, improve through iterative execution, are evaluated by mentor agents or humans in the loop, and turn completed work into reusable work experience and data to improve future agents.

⭐ 1.3kPython

The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all Agent Skill / Claude Code plugin.

⭐ 1.1kTypeScript

The AI agent with a wallet — spends USDC autonomously to get real work done. Apache-2.0, TypeScript.

⭐ 624TypeScript

Daydreams is a set of tools for building agents for commerce

⭐ 611TypeScript

The first agentic payment network: policy-controlled, gasless, and real money-ready. OmniClaw CLI + Financial Policy Engine let autonomous agents pay and earn safely at machine speed.

⭐ 575Python

Agent behavior that compiles

⭐ 566Rust

The A2A x402 Extension brings cryptocurrency payments to the Agent-to-Agent (A2A) protocol, enabling agents to monetize their services through on-chain payments. This extension revives the spirit of HTTP 402 "Payment Required" for the decentralized agent ecosystem.

⭐ 541Python

Open Source AI trading agent that operates autonomously across 1000+ markets - Polymarket, Kalshi, Binance, Hyperliquid, Solana DEXs, 5 EVM chains. Scans for edge, executes instantly, manages risk while you sleep. Agent commerce protocol for machine-to-machine payments. Self-hosted. Built on Claude.

⭐ 506TypeScript

Keep reading

Monetize with per-call pricing →x402 vs traditional billing →Build an API paywall →
Other alternatives: Stripe · PayPal · Lemon Squeezy · Paddle · Coinbase Commerce · Gumroad · Razorpay

Frequently asked questions

Can Chargebee bill AI agents per API call?

Chargebee can meter usage but still frames it inside subscription plans and invoice cycles built for human accounts. Agent-native rails settle each request in real time with no plan or invoice — the projects above implement that.

What is the agent-native equivalent of subscription billing?

Per-request settlement via x402: instead of a monthly plan, each call carries its own payment (HTTP 402 → pay USDC → access). It removes signup, proration and dunning entirely for machine customers.