Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/fuseio/fuse-docs/llms.txt

Use this file to discover all available pages before exploring further.

Fuse AI is Fuse’s native infrastructure layer for agentic payments, built for a world where on-chain economic activity is increasingly driven by autonomous agents rather than humans. It sits on the same high-throughput, low-cost rails that power Fuse’s consumer and business applications, giving AI agents real settlement capability with sub-2-second finality and transaction costs measured in fractions of a cent.

Why AI agents need a blockchain

AI agents are becoming economic actors. They transact, hire, and settle work autonomously, but they cannot open bank accounts, satisfy KYC requirements, or hold a credit card. They can, however, own a wallet. Fuse provides the settlement infrastructure that makes that wallet useful: native support for emerging agentic commerce standards, programmable smart accounts with no manual onboarding, and stablecoin rails optimised for micropayments.

Key capabilities

Deploy agent wallets

Spin up ERC-4337 smart accounts for AI agents programmatically via the FuseBox SDK — no KYC friction, no manual onboarding, full programmability.

Machine-to-machine payments

Settle micropayments between agents — invoices, task completions, API calls — at the speed and cost that make agent-to-agent commerce economically viable.

Agentic protocol support

Native support for the emerging protocol stack for agentic commerce across multiple interoperability standards.

MCP server integration

A dedicated Fuse MCP server exposes Fuse’s payment and account infrastructure to any AI tool, agent framework, or application on the network.

Supported agentic payment standards

Fuse natively supports the emerging protocol stack for agentic commerce. These standards make it possible for AI agents built on different frameworks to transact with each other without custom integration work.
StandardDescription
x402HTTP-native micropayments — agents pay for API calls and data at the protocol layer.
MPPMachine-to-machine payment protocol for autonomous agent transactions.
UCPUniversal commerce protocol providing a common layer for agent-initiated purchases.
ACPAgent checkout protocol — the checkout layer inside AI interfaces and agent pipelines.
ERC-8183Ethereum standard for agentic commerce, actively being implemented on Fuse.
ERC-8183 is an Ethereum-level standard for agentic commerce. Fuse is an active implementer, meaning agent wallets on Fuse will be interoperable with the broader ERC-8183 ecosystem as it matures.

MCP server for agent framework integration

A dedicated Fuse MCP (Model Context Protocol) server is in development. Once available, it will expose Fuse’s payment and account infrastructure as MCP tools, allowing any MCP-compatible AI agent framework to:
  • Create and manage smart wallets for agents
  • Send and receive payments on Fuse
  • Query balances and transaction history
  • Interact with deployed smart contracts
The MCP server is currently in development. Watch the Fuse GitHub organisation for release announcements.

Deploy agent wallets with FuseBox SDK

Agent wallets are standard ERC-4337 smart accounts created via the FuseBox SDK. No special agent-specific setup is required — the same FuseSDK.init call used for human wallets works for agent wallets.
import { FuseSDK } from "@fuseio/fusebox-web-sdk";
import { ethers } from "ethers";

// Each agent has its own credentials (private key)
const agentCredentials = new ethers.Wallet(agentPrivateKey);
const apiKey = "YOUR_FUSEBOX_API_KEY";

const fuseSDK = await FuseSDK.init(apiKey, agentCredentials, {
  withPaymaster: true,
});

const agentWalletAddress = fuseSDK.wallet.getSender();
console.log(`Agent wallet: https://explorer.fuse.io/address/${agentWalletAddress}`);
Because the wallet is an ERC-4337 smart account, it supports batch transactions, programmable access controls, and gas sponsorship — all useful properties for autonomous agent operation.

Machine-to-machine payment example

The following example shows one agent transferring a stablecoin to another agent as payment for a completed task:
import { ethers } from "ethers";

const usdcAddress = "0x28C3d1cD466Ba22f6cae51b1a4692a831696391A"; // USDC on Fuse
const recipientAgentAddress = "0xAGENT_B_WALLET_ADDRESS";
const paymentAmount = ethers.parseUnits("0.50", 6); // 0.50 USDC

const res = await fuseSDK.transferToken(
  usdcAddress,
  recipientAgentAddress,
  paymentAmount
);

const receipt = await res?.wait();
console.log(`Payment settled: https://explorer.fuse.io/tx/${receipt?.transactionHash}`);
With withPaymaster: true, the sending agent does not need to hold FUSE for gas. Your Operator account’s Paymaster covers the fee, keeping agent wallets focused purely on their payment token balances.

Next steps

FuseBox SDK

Full SDK reference for creating wallets, sending tokens, and more.

FuseBox setup

Get your API key and configure Paymaster for sponsored transactions.

Build docs developers (and LLMs) love