Sponge

• Name: Sponge
• URL: https://paysponge.com/
• Category: hosted agent wallet control plane / paid-request gateway wrapper
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Sponge is hosted wallet ops for agents with paid-request rails bolted on. The point is wallet provisioning, API-keyed signer access, and gateway pricing around those wallets. Not a new payment rail.
• What it does:
  • Gives agents hosted wallets and API-key access for balances, transfers, swaps, bridges, and other multichain wallet actions across Ethereum, Base, Tempo, and Solana
  • Splits control between SpongeWallet runtime access for individual agents and SpongePlatform fleet controls for agent creation, provisioning, and key rotation under higher-order platform credentials
  • Supports non-interactive agent keys, interactive device-flow login, and local credential caching for CLI or SDK use
  • Wraps paid-request flows through x402 and MPP so agents can pay for APIs and other services directly from the hosted wallet surface
  • Runs Sponge Gateway, which sits in front of upstream APIs so operators can meter, price, and expose them to agents without changing the upstream service
  • Ships MCP, CLI, SDK, OpenAPI, and agent-client setup surfaces, plus onramp and trading endpoints that make the wallet-ops bundle broader than a thin paywall helper
• Key claims:
  • Sponge is mostly a hosted signer and wallet-ops note, not an x402 note.
  • The useful split is runtime agent keys versus platform-level provisioning keys. That is where the control lives.
  • Sponge Gateway is the sharper part of the stack: pricing, metering, and upstream API exposure sit there, not in the payment rail.
  • The broad docs surface matters because it shows real operator packaging around wallets, not just a tiny paid-request demo.
• Whitepaper: No canonical standalone Sponge whitepaper or litepaper surfaced in this pass. The strongest current sources of truth are the official site, docs, llms.txt index, Gateway docs, authentication docs, payments quickstarts, OpenAPI specs, and public GitHub org / SDK repo; see ../whitepapers/sponge-primary-sources-2026-04-28.md.
• Sources:
  • https://paysponge.com/
  • https://docs.paysponge.com/
  • https://docs.paysponge.com/llms.txt
  • https://docs.paysponge.com/authentication
  • https://docs.paysponge.com/gateway
  • https://docs.paysponge.com/quickstart-payments
  • https://github.com/paysponge
  • https://github.com/paysponge/paysponge-sdk

Internal linkages

• Strongest upward reads: turnkey and x402.

Control surface

• The leverage sits in platform-key issuance, per-agent wallet creation, signer access policy, gateway metering, and which chains or payment methods the operator exposes behind one runtime-facing surface.

• Real wallet-and-gateway power. Still packaged above stronger signer infrastructure and paid-request standards.

• Last reviewed: 2026-06-18 UTC