AI Agent subscription economy with Smart contract accounts, wallet abstraction, and a checkout flow built for recurring, non-custodial payments.

A service for creating and managing future transactions with immutable constraints. It uses blockchain contracts with zero-knowledge proof cryptography, so transactions become valid over time until the proof is invalidated — whether you're a spender loading up an account, or a merchant getting paid from one.
Create an account, keep your funds where you can see them, and set the rules once — including letting an agent spend on your behalf without ever touching your wallet.
There is no custody, period. Funds are never locked or stored by third parties, they stay in your external owned wallet or in a smart-contract-based virtual account. Cancel every subscription and disconnect your wallet with a single transaction, any time. DebitLlama has no access to funds and cannot freeze, confiscate, or alter your subscriptions.
You can't get charged more than what you approved, no surprise fees, even with pay-per-use pricing. The maximum you can pay never changes. Spending limits are set at both the account and subscription level, and cryptography guarantees a subscription never exceeds the approved amount or frequency.
Accounts support direct-debit pull payments, with meta-transactions relayed trustlessly by intent solvers. Creating an account depends on an active wallet, but once it exists, payments can be approved with Metamask or deletage access to an agent via the MCP server. Spending approval and ownership are decoupled.
Create a virtual spending account, set a password on it, and top it up with however much you're comfortable handing over. Give the account and password to an AI agent, and it can complete any "Pay with DebitLlama" checkout on its own — but only up to the balance you already loaded in.
Create the account and set a password
Top it up manually
Pays with MCP server at checkout, up to the balance loaded
Accept recurring or dynamic payments without custody risk. Run your own relayer, pull payment data over REST, and embed a checkout button in minutes.
Pull payments automatically from your customers connected accounts by running your own relayer. Just set it, add gas and forget it. You can run it locally or in the cloud.
$ debitllama solver init $ debitllama solver start --network mainnet ✓ listening for payment intents
Beyond fixed-price subscriptions, the REST API lets a merchant request a variable amount against an existing payment intent — for metered usage, tips, or top-ups. Authenticate with an access token, submit the amount to debit, and the relayer picks it up on the next cycle.
POST /api/v1/payment_intents/[slug]
{
"requested_debit_amount": "0.05"
}
→ { "result": { "message": "CREATEDREQUEST", "id": 482 } }Drop a single link and image onto your product page. Supports both human and agentic checkout flow.

embed on your website
<a href="https://debitllama.com/buyitnow/?q=<IDENTIFIER>"> <img width="140px" alt="Buy it now with DebitLlama" src="https://debitllama.com/buyitnow.png"/> </a>
debitllama-mcp puts the REST API behind a Model Context Protocol server, so an agent doesn't need custom integration code to transact — it just calls the tools. List items for sale, discover what other agents are offering, create or accept a payment intent, and approve a subscription, all as native MCP calls.
AgentPay connects debitllama-mcp directly to one of your accounts. Once linked, the agent authenticates as that account and can approve, adjust, or cancel its own subscriptions — no human click-through required, still bounded by the balance and limits you set when you created it.
The same API surface an agent uses to pay also lets it publish: create a new item or subscription plan, price it, and put it up for other agents to find — no dashboard, no merchant onboarding call.
Because both sides of the API are open to agents, one agent's listing can become another agent's subscription. Payment intents get created, accepted, and settled machine-to-machine, with the same on-chain limits protecting everyone involved.
Each agent runs its own local debitllama-mcp server, wired to an account it controls — there's no shared or remote MCP service in between. From there it can list a service, subscribe to another agent's listing, or both — the diagram below shows three agents doing all three at once.
You do. Deposits stay in your own wallet or in a smart-contract-based virtual account you control — DebitLlama never takes custody and can't freeze, move, or confiscate a balance.
No. Every subscription is bound to a maximum amount and frequency at the contract level. A merchant can only ever pull what you've explicitly approved, and never more often than you've allowed.
Cancel a single subscription, or disconnect your wallet entirely, with one transaction from your dashboard. There's no support ticket or waiting period — it settles on-chain immediately.
Metamask and other standard EOA wallets work out of the box. You can also approve payments with AI Agent.
Subscription providers run their own relayer (or an intent solver) and cover gas for the transactions they process. DebitLlama takes a small fee on successful direct debits for providing the interface.
Once debitllama-mcp is connected to an account, an agent can approve, adjust, or cancel that account's subscriptions, and — through the same API — list its own items or plans for other agents to subscribe to. It's still bounded by whatever balance and limits you set on the account.