CREATE
Generate a disposable wallet in seconds.
Create a temporary Solana payment identity for one task or session. Give it a fixed USDC budget, payment limits, merchant rules and expiry β then let the agent pay supported x402 services without exposing your primary wallet.
Generate a disposable wallet in seconds.
Add USDC with your budget and rules.
Let your agent transact within limits.
Retire it. Funds swept. Identity disabled.
An API can answer an agent with 402 Payment Required instead of asking for a card, login or subscription. SI/BURN reads the payment request, checks the network, USDC amount, cumulative budget, merchant permission and Burner expiry, and signs only when the request is allowed. The x402 facilitator verifies and settles the payment on Solana; the paid resource is then returned to the agent so its task can continue.
A real end-to-end browser/development lifecycle on Solana mainnet.
| TXN | SIGNATURE | DETAIL |
|---|---|---|
| Spend (x402) | 3mV1o7...h1oh β | Paid live AI endpoint β 0.008 USDC |
| Sweep USDC | 3g9rj6...daGuY β | Remaining 0.012 USDC swept |
| Close account | 67oicR...y8Ftd β | USDC token account closed |
| Sweep SOL | 5zfiYZ...phtNp β | Remaining SOL swept β final balance 0 |
Built for the machine economy.
Limit spend per task or session.
Time-bound permissions keep agents in check.
Allow specific services like x402, block the rest.
Sweep funds and disable identity when done.
Real utility. Real demand.
Pay for APIs, data, compute and more automatically.
One-time purchases without exposing your main wallet.
Give agents a budget and let them work within it.
Separate budgets and permissions per task or agent.
SI/BURN started with a simple thesis: autonomous agents need disposable payment identities. The Burner Lab is live, the Agent API is live, and x402 payments are working on Solana mainnet. SI/BURN is the token around that ecosystem.
PENDING PUMP LAUNCHAlways verify the contract address shown on siburn.xyz before interacting with the token. SI/BURN product access is currently open; token-enabled tiers or additional utility may be introduced only when implemented.
The Agent API is live in beta at api.siburn.xyz. Software can create temporary Burner identities, monitor them, make policy-controlled x402 purchases and retire them programmatically.
POST /v1/burnersPOST /v1/burners/:id/fetchGET /v1/burners/:idPOST /v1/burners/:id/burnPOST https://api.siburn.xyz/v1/burners
Authorization: Bearer sib_...
{
"budget": "10.00",
"max_payment": "0.25",
"expires_in": 3600,
"return_address": "YOUR_SOLANA_WALLET",
"merchants": ["payai.agentstools.dev"]
}
β Burner address + policy + expiry
The API-created Burner paid a live x402 endpoint 0.008 USDC on Solana mainnet, received the purchased resource, then retired with final balances of 0 USDC / 0 SOL.
Beta security model: SI/BURN uses a policy-controlled hosted signer for API Burners. Raw Burner private keys are not returned to agents. The beta enforces network, USDC asset, merchant hostname, per-payment cap, cumulative budget and expiry before signing. Production hardening will move signing into a dedicated constrained signing/KMS layer before supporting material balances.
SI/ is a family of infrastructure and products built for autonomous agents. Burners begin with disposable payment identities; the namespace can expand as real agent needs emerge.
Create an individual developer key, then create your first disposable payment identity in minutes. Your full API key is displayed once; SI/BURN stores only a hash.
SI/BURN cannot display the full key again.
export SIBURN_API_KEY="sib_live_..."
curl -s https://api.siburn.xyz/v1/burners \
-H "Authorization: Bearer $SIBURN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"budget":"1.00",
"max_payment":"0.05",
"expires_in":3600,
"return_address":"YOUR_SOLANA_WALLET",
"merchants":["payai.agentstools.dev"]
}'
Send USDC to the returned Burner address. Use POST /v1/burners/:id/fetch for approved x402 purchases, then POST /v1/burners/:id/burn to return remaining assets and retire the identity.
A temporary Solana payment identity for a single autonomous task or session. You fund only the budget the agent needs, apply SI/BURN spending rules, and retire the identity when the job is finished.
Burn returns remaining funds to the nominated wallet, closes disposable token accounts where practical, and retires the temporary signing credential. It does not delete or hide transactions already recorded on Solana; those remain publicly verifiable.
No. Solana transactions that have already settled remain public and verifiable. In SI/BURN, βBurnβ means the temporary identity is retired: remaining assets are returned, disposable token accounts are closed where possible, and SI/BURN removes the active signing credential from service.
Basic Burner access is intended to remain open. Token-enabled tiers and advanced capabilities can be added as the product evolves.
x402 is a machine-payment flow built around HTTP 402 Payment Required. A paid service can request payment from software; SI/BURN checks that request against the Burner policy before allowing an approved USDC payment and returning the resource to the agent.
Yes. The SI/BURN Agent API is live in beta at api.siburn.xyz. Authenticated software can create, monitor, spend from and retire temporary Burners programmatically. The current beta supports policy-controlled x402 payments on Solana mainnet; SDK and MCP wrappers are the next developer interfaces.