Docs

API

Base URL: https://dustjar-production.up.railway.app. The read endpoints below need no key, because they expose only what is already public on chain and rate-limiting an address lookup protects nobody. A machine-readable description is at /v1/openapi.json.

What is live now

EndpointWhat it answers
GET /v1/rent/minimumsToday's rent-exempt minimums by account size, and the surplus a token account made before September 2026 is holding. Read this rather than hardcoding: SIMD-0437 lowers it in phases.
GET /v1/wallet/{address}/reclaimableWhat one wallet can reclaim: empty accounts, rent surplus, withdrawable stake, abandoned program buffers, as one total plus its parts.
GET /v1/leaderboardWallets ranked by SOL returned to their owners, with all-time totals.
GET /v1/wallet/{address}/claimsOne wallet's claim history, each row naming a signature anyone can check.
POST /v1/sweep/planUnsigned, already-simulated transactions for the owner to sign. The server never signs.
POST /v1/sweep/sendRelay a signed transaction and wait for it to confirm.

For agents

An MCP server is served at /mcp, speaking the JSON-RPC subset MCP clients need. It offers three tools: scan_wallet, rent_minimums and leaderboard.

Every MCP tool is read-only, deliberately. An agent can find out what a wallet is owed and report it. It cannot build, sign or send anything, because an agent that moves money on someone behalf is a different product with a different risk. Claiming always happens at dustjar.xyz, where the owner approves in their own wallet.

Still to come

What it will never do

The intended users are wallets, portfolio trackers and trading platforms that want cleanup built into their own product. If that is you, tell us what you need before we finish designing it.

All docs · Questions · Scan a wallet