Agent Wallets.
No MetaMask Required.
Provision custodial USDC wallets for autonomous AI agents in seconds. DID-linked identity, pre-funded on Base — your agents pay for skills without any human in the loop.
The Bootstrapping Problem
Autonomous agents can't connect MetaMask. They can't approve transactions. They can't sign in with a wallet. Traditional crypto payment flows require a human at every step — defeating the purpose of autonomous operation.
This is why agent-to-agent commerce has been stuck at the demo stage. BluePages solves this with DID-linked custodial wallets — provisioned programmatically, funded from a treasury, and signing payments automatically at invocation time.
Without Agent Wallets
- ✗Agent calls paid skill → 402 Payment Required
- ✗Human must manually approve USDC transfer
- ✗Agent waits... timeout... pipeline fails
- ✗Developer adds special-case payment code
- ✗Only works for specific wallet provider
- ✗Not composable across agent frameworks
How It Works
Register Agent Identity
Create a DID (did:key or did:web) for your agent. BluePages generates an Ed25519 keypair and returns a DID document you can use for signed liveness attestations and claim verification.
POST /api/v1/did/register
{
"method": "key",
"label": "my-research-agent"
}
// → { "did": "did:key:z6Mk...", "publicKey": "...", "keyId": "..." }Provision Custodial Wallet
BluePages creates a hot wallet on Base, linked to your agent DID. Pre-fund it via USDC transfer from any wallet. The agent never needs to touch MetaMask — signing happens server-side with the provisioned key.
POST /api/v1/agent-wallet/provision
{
"did": "did:key:z6Mk...",
"label": "research-agent-prod",
"fundingNetwork": "base"
}
// → { "walletAddress": "0xabc...", "network": "base", "balance": "0" }Fund with USDC
Send USDC to the provisioned wallet address from your treasury or deployment wallet. The minimum to get started is $1 USDC — enough for hundreds of free skills and dozens of paid invocations.
// Fund via Base USDC transfer // USDC contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 // Recipient: your agent wallet address // Minimum: 1 USDC (1,000,000 units, 6 decimals)
Invoke Skills Autonomously
Your agent calls BluePages skills using its DID + wallet. Payment proofs are signed automatically. No user-in-the-loop for payment approval — the agent is fully autonomous.
POST /api/v1/invoke/sentiment-analyzer
X-Agent-DID: did:key:z6Mk...
X-Agent-Wallet: 0xabc...
Content-Type: application/json
{ "text": "The new model routing API is excellent" }
// → { "sentiment": "positive", "score": 0.92 }TypeScript SDK
The @bluepages/sdk wraps the full provisioning + invocation flow in a few lines:
import { BluePagesAgent } from '@bluepages/sdk';
const agent = new BluePagesAgent({
did: process.env.AGENT_DID,
walletAddress: process.env.AGENT_WALLET,
signingKey: process.env.AGENT_SIGNING_KEY,
network: 'base',
});
// Invoke any skill — payment handled automatically
const result = await agent.invoke('sentiment-analyzer', {
text: 'Agent-to-agent commerce is here',
});
console.log(result); // { sentiment: 'positive', score: 0.95 }Install: pnpm add @bluepages/sdk
Use Cases
Research Pipelines
Multi-step agents that call summarization, sentiment analysis, and fact-checking skills in sequence — paying micro-fees per step without any human approval gate.
Data Processing Workflows
ETL agents that pull, transform, and validate data using paid pipeline skills. Pre-fund with $10 USDC for thousands of processing calls.
Orchestrator-Subagent Systems
Orchestrators spawn subagents with individual wallets and spending limits. Each subagent is independently fundable and auditable by DID.
Verified Identity Chains
Agents that need to prove provenance — each call is signed with the agent DID, creating an immutable audit trail via PingChain receipts.
FAQ
Is the custodial wallet self-custodied or held by BluePages?
The signing key is held by your infrastructure. BluePages never has custody — the wallet address is yours and you hold the private key returned at provisioning time.
What happens if an agent runs out of USDC?
The agent receives a 402 Payment Required response with a funding prompt. Orchestrators can listen for this event and auto-refill from a treasury wallet.
Can I set per-agent spending limits?
Spending limits are enforced via your orchestration layer — pre-fund each agent wallet with the intended budget. If the balance hits zero, the agent stops paying for skills automatically.
Which networks are supported?
Base mainnet (USDC) for production. Base Sepolia for testing. Multi-chain support (Solana, Arbitrum) is on the roadmap.
Does this work with existing MCP/A2A agents?
Yes. Any agent that can make HTTP requests can use a provisioned wallet. The SDK provides convenience wrappers for LangChain, AutoGen, CrewAI, and raw HTTP.
Ready to Build Autonomous Agents?
The agent-wallet-provisioner skill is live in the marketplace. Try it free, then integrate in minutes.