Cowrie Research

sponge-primary-sources-2026-04-28

4 min read

Sponge primary-source snapshot

Fetched: 2026-04-28 UTC

1) Official homepage

Source: https://paysponge.com/

Selected excerpts from the official site:

The easiest way for agents to hold and spend money, and for businesses to sell directly to them.

Give your agent an account.

Sell directly to agents.

Additional signals from the source:

  • The homepage clearly frames Sponge around AI agents rather than human wallets first.
  • It also reveals a two-sided market ambition: agent wallets on one side, agent-payable services on the other.
  • The product language is broader than a wallet SDK because it already includes business monetization and payment acceptance.

2) Docs welcome page

Source: https://docs.paysponge.com/

Selected excerpts from the official docs:

Give your agents wallets for transfers, swaps, bridges, Hyperliquid trading, and x402 and MPP payments across EVM and Solana.

Early access. Things may change.

Additional signals from the source:

  • This page is the clearest compact description of Sponge’s current product surface.
  • The supported networks list (Ethereum, Base, Tempo, Solana) and Hyperliquid market support show that Sponge is deliberately multi-chain and trading-adjacent, not only an API-payment wrapper.
  • The docs also foreground multiple operator personas: individual agents, backend platforms, and businesses exposing paid endpoints.

3) Documentation index (llms.txt)

Source: https://docs.paysponge.com/llms.txt

Selected signals from the official index:

  • The docs expose agent CRUD, wallet balance and detail endpoints, transfer and bridge APIs, Base and Solana swaps, Hyperliquid trading, Stripe and Coinbase onramp sessions, x402 / MPP payment flows, gateway setup, and public OpenAPI specs.
  • The breadth of the index is one of the strongest clues that Sponge is a wallet-and-payments control plane rather than a narrow SDK.
  • The presence of llms.txt and machine-readable OpenAPI artifacts also shows explicit support for agentic and machine-consumer workflows.

4) Authentication docs

Source: https://docs.paysponge.com/authentication

Selected excerpts from the official docs:

Device flow, API keys, master keys, and credential storage.

The SDK supports three ways to authenticate.

Master keys are used with the REST API directly, not with SpongeWallet.connect().

Additional signals from the source:

  • The agent-key vs master-key split is a high-signal architecture clue.
  • Sponge is not only a runtime wallet; it has a control plane for provisioning and managing many agents from a backend.
  • Local credential caching and device-flow login show it is designed for both interactive and automated agent environments.

5) Payments quickstart

Source: https://docs.paysponge.com/quickstart-payments

Selected excerpts from the official docs:

Make x402 and MPP payments from agents with the Sponge SDK.

paidFetch() is the highest-level helper. It lets Sponge negotiate the payment flow for you.

MPP is available through the SDK.

Additional signals from the source:

  • This page makes clear that paid API consumption is a first-class workflow, not a side feature.
  • Sponge abstracts both x402 and Tempo-native MPP payment flows behind SDK helpers and CLI commands.
  • The examples also confirm that Sponge is intentionally built to sit inside agent workflows, including Claude-style MCP usage.

6) Gateway docs

Source: https://docs.paysponge.com/gateway

Selected excerpts from the official docs:

Turn any API into paid endpoints, priced, metered, and payable by agents, with no code changes to your upstream.

Sponge Gateway sits in front of your API and makes each route payable via x402 or MPP.

Additional signals from the source:

  • This is the clearest page for understanding Sponge’s second major product surface beyond wallets.
  • The gateway positions Sponge as merchant/payment infrastructure for the agent economy, not just as a wallet SDK for bots.
  • The explicit MCP integration instructions for Claude Code, ChatGPT, Codex CLI, and Cursor underline the agent-native distribution strategy.

7) Public GitHub organization and SDK repo

Sources:

Selected excerpts from the public sources:

SDK for creating and managing wallets for AI agents with Claude Agent SDK integration

SpongeWallet: the agent-scoped runtime client

SpongePlatform: the platform control-plane client for creating and managing many agents

Additional signals from the source:

  • The GitHub org confirms multiple product surfaces: SDK, docs, wallet skills, and x402/Tempo-related repos.
  • The SDK README is one of the clearest sources for the runtime-vs-control-plane distinction.
  • Public repos reinforce that Sponge is packaging itself for agent developers rather than only for traditional crypto developers.

Notes

  • Sponge appears best cataloged as agent wallet and payments infrastructure / x402-MPP gateway / wallet-control-plane for AI agents.
  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The highest-signal categorization clues are the split between SpongeWallet and SpongePlatform, the paid-request abstractions for x402 and MPP, and the Gateway product that turns ordinary APIs into agent-payable endpoints.

Graph View