Pricing
For holders
Claim your share of gold, the S&P 500 and US Treasuries whenever you want. You pay only Solana network gas and the one-time token account rent for each asset (fractions of a cent plus ~0.002 SOL per token account, charged by Solana, not by VaultBags).
Locking $VAULT via Streamflow earns up to 50% extra (1.5x) on the locked tokens. VaultBags charges nothing; Streamflow's own minor account costs apply.
Voting, the holder raffle, report cards and the Vault Intelligence dashboard with the AI analyst are included for holders.
For Bags creators
Launch through the launcher or point your token's fee share at VaultBags. Three dedicated treasury wallets, automatic conversion and a public treasury page are provisioned automatically on first fees.
Of claimed fees, taken once per cycle before conversion. Covers the automation that collects, converts and distributes around the clock.
External projects (everything except $VAULT itself) contribute 5% of the SOL before conversion. It buys and permanently locks $VAULT liquidity on Meteora, so every integrated project deepens the protocol's own floor. $VAULT pays no protocol fee.
For machines (the Vault Agent)
Every read-only tool (allocation, signals, treasury, receipts, the RWA registry, The Meter) is free and unauthenticated, rate-limited per caller. Start at /llms.txt or /api/openapi.
POST a question to /api/agent/ask. Anonymous callers get 10 per day; a wallet holding at least 10,000 $VAULT (held or locked), signed in, gets 60 per day.
When the free lane is exhausted the endpoint answers HTTP 402 with spec-shaped payment requirements.
Technical detailHide the detail
Settle the USDC transfer on Solana (with the commit-reveal memo binding) and retry with the X-PAYMENT header: one settled payment buys exactly one answer, and paying callers get rolling conversation memory.
Every 402 also carries a PAYMENT-REQUIRED header in the x402 v2 standard, so an off-the-shelf x402 client pays with no VaultBags-specific code: it signs the USDC transfer without sending it and retries with the PAYMENT-SIGNATURE header.
Technical detailHide the detail
Coinbase's facilitator checks the payment against these exact terms and pays the Solana network fee, and the transfer is sent only once the answer or export is ready, so a request that fails before then costs nothing. Covers the question, the ledger and the registry batch; credit packs are bought through the native lane.
One on-chain payment mints a prepaid balance ($0.04 per question, 20% off). The purchase returns a one-time credit token; spend it on later calls with the X-CREDIT-TOKEN header, no further transactions. Guard it like an API key; it never expires.
The complete receipted decision history in one machine-readable export: every daily allocation since inception with its raw signals, convictions, drivers and on-chain receipt, plus the brain-vs-flat and shadow measurement series. Also payable with 5 pack credits at GET /api/agent/ledger.
Every certified tokenized RWA with a live market read for each, in one call, at GET /api/agent/rwa-registry-live. Also payable with 2 pack credits. The registry list and single lookups stay free.
Every response settled on-chain via X-PAYMENT or PAYMENT-SIGNATURE carries an X-X402-Receipt header: a signed (RS256) receipt naming the transaction, the payer, the amount, the destination wallet, the asset and the resource, and what the call delivered: the sha256 of the question and of the answer exactly as served, with the tools the agent read for it, or the sha256 of the export.
Technical detailHide the detail
It verifies offline against /.well-known/jwks.json with no call back to VaultBags, so whoever holds the answer and its question can show they are the ones that were paid for, for as long as the key that signed the receipt stays published. Credit spends carry none (there is no per-call transaction to point at). Check one, with the response and the question you saved: npx vaultbags-cli@0.7.0 verify receipt <jwt> --body=response.json --question=question.txt.
Solana network fees and token account rent are charged by the network itself and apply to any on-chain action. Full mechanics in the docs; live protocol numbers on The Meter.