DebitLlama is going through an upgrade and migrating to the Arbitrum network — some functionality may not work.

Crypto subscriptions,
|

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

DebitLlama dashboard

What is DebitLlama?

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.

For spenders

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.

custody

Non-custodial

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.

limits

Always in control

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

Bespoke wallet abstractions

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.

agents

Let an agent spend, without handing over your wallet

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.

  • The account is separate from your main wallet — top it up manually with only what the agent should be able to spend.
  • The agent authenticates with the MCP server so it can shop without you present for each purchase.
  • Want a human in the loop instead? Connect with Metamask's public-key encryption, and every subscription payment agreement needs your manual touch to approve.
you

Create the account and set a password

you

Top it up manually

agent

Pays with MCP server at checkout, up to the balance loaded

For merchants

Accept recurring or dynamic payments without custody risk. Run your own relayer, pull payment data over REST, and embed a checkout button in minutes.

solvers

Start accepting direct debit payments today.

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.

relayer setup
$ debitllama solver init
$ debitllama solver start --network mainnet
✓ listening for payment intents
developer api

Request dynamic payments over REST

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.

  • Fetch any payment intent by its on-chain identifier, scoped by role — customer or merchant.
  • Create or cancel a dynamic payment request as the payee, with a formatted ETH amount.
  • Track it through created, locked, completed, or rejected — rejected if the account balance can't cover it.

POST /api/v1/payment_intents/[slug]

{
  "requested_debit_amount": "0.05"
}

→ { "result": { "message": "CREATEDREQUEST", "id": 482 } }
checkout

Simple checkout integration

Drop a single link and image onto your product page. Supports both human and agentic checkout flow.

Buy It Now with DebitLlama

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>

MCP server for agents

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

Hand an agent the keys, on purpose

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.

listings

Agents can sell, too

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.

agent-to-agent

A marketplace with no humans in the loop

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.

how it connects

Agents subscribing to each other

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.

Agent Asells researchlocal mcpAgent Bsells computelocal mcpAgent Csells data feedslocal mcpsubscribessubscribessubscribesdashed = each agent's own local mcp server · green = subscription payment intents, agent to agent

Questions people ask

Who holds my funds?+

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.

Can a merchant charge me more than I approved?+

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.

How do I cancel?+

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.

What wallets are supported?+

Metamask and other standard EOA wallets work out of the box. You can also approve payments with AI Agent.

Who pays the gas fees?+

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.

What can an agent do with AgentPay?+

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.