Why AI agents pay with HBAR
An agent that pays a cent per API call needs a fee far below a cent and a spending cap it cannot break. Here is how both work on Hedera.
Content reviewed on

Why agents need a different way to pay
What an agent needs, and what Hedera provides
| What the agent needs | Why it matters | On Hedera |
|---|---|---|
0.0.456858 | ||
Fees small enough for micropayments
Final settlement in seconds
Spending limits a person sets once
- Separate agent account
Create an account for the agent and fund it with only what it needs. If something goes wrong, the loss is capped at that balance. - Allowance
Keep funds in your own account and approve the agent's account to spend up to a set amount of HBAR, a token or specific NFTs. The cap is a running total, not a daily limit, and the agent can send within it to any account, so size it for the job. You can lower or remove the allowance at any time. - Threshold key
For a treasury account, require several signatures, such as the agent's key plus a person's. The agent can propose a scheduled transaction that only runs once the other signatures are added.
An audit trail agents cannot edit
Agent safety needs an independent record
Open tools for agent builders
Hedera Agent Kit: an open source toolkit with adapters for LangChain, the Vercel AI SDK, ElizaOS, Google's Agent Development Kit and MCP, so an agent can transfer HBAR, work with tokens and write to consensus topics. It can also hand back unsigned transactions for a person to sign. See the Hedera Agent Kit. HCS-10 OpenConvAI: an open standard from the Hashgraph Online community for agents to register, find each other and exchange messages over consensus topics. Read the HCS-10 standard. x402: an open standard that revives the HTTP 402 Payment Required status, so an API can ask for a payment and an agent can pay and retry in one request cycle. Hedera support was added to the x402 project in 2026, with payments in HBAR or Hedera tokens and a facilitator that can cover the network fee. See the x402 project.
Safeguards before you let an agent pay
Start on testnet. Test HBAR has no value, so mistakes cost nothing. Give the agent its own account or an allowance, never your main key. Treat every web page, NFT description and message the agent reads as data, not instructions. Prompt injection is the most likely way an agent is tricked into paying. Log each payment with a memo or a consensus topic message, and review the history on a mirror node. Set a review point: above a certain amount, require a person's signature through a threshold key.
Agents and NFTs on SentX
- Why HBARThe case for HBAR, starting with what one transfer costs.
- Start building with Hedera NFT dataMirror nodes, the SDK and marketplace data.


