Sponge

Agent-nativePricing not documented

Wallets, agent spending controls, and payment gateways for the agent economy

Overview

About Sponge

This summary uses submitted and public product material. Only source-mapped claims are documentation reviewed.

Sponge is financial infrastructure for agents and businesses transacting with them. Its current product spans agent wallets, payment gateways, REST APIs, wallet skills, transfer and swap flows, x402 paid API access, and owner-managed spending controls.

Features

  • Agent wallet accounts for holding and moving funds across supported chains
  • Business gateway for onboarding agents and accepting payments without a human checkout flow
  • REST API for balances, transfers, swaps, bridges, funding requests, and transaction history
  • x402 payment creation for paid API access and machine-native payment flows
  • Spending controls, allowlists, and owner approval flows for safer delegated spending

So agents can…

  • Pay for services or data within pre-approved guardrails instead of asking a human to click checkout
  • Transfer funds to vendors, creators, or other agents while keeping an audit trail
  • Combine planning and payment in one loop, for example buying data before executing a trade or workflow

Listing decision

Why Sponge is listed

Sponge gives agents their own programmable financial accounts and payment actions, and lets merchants expose machine-payable endpoints, making autonomous agent transactions the product’s primary design rather than an add-on.

Before you choose

Fit and limitations

Best for

Agents that need controlled wallets, card or bank payment capabilities, x402/MPP purchases, transfers, swaps, or markets, and API businesses that want to sell metered endpoints to agents through a managed gateway.

Known limitations

Financial actions involve real funds, credentials, supported chains, third-party providers, and in some cases card onboarding or KYC. Operators must apply conservative limits, protect sensitive card and API-key data, review every published gateway route, and account for legal, tax, compliance, counterparty, and market risk.

Not yet verified

No public Sponge fee schedule or plan page was found in the reviewed first-party sources, so product pricing remains unknown; prices configured for third-party gateway endpoints do not establish Sponge’s own fees. The terms say features may be beta and may change; custody model, geographic eligibility, service-level commitments, and independent control effectiveness were not established.

Sources

Sources and verification

First-party unless marked otherwise. Each link supports only its adjacent claim.

  1. Sponge homepage — agent wallets and merchant payments

    Sponge presents hosted financial infrastructure for agents to hold and spend through cards, bank accounts, and crypto, with programmable spending controls and a gateway for merchants accepting agent payments.

    official product page · accessed Sep 3, 2026
  2. Sponge Wallet documentation — wallet capabilities and interfaces

    The wallet documentation covers stablecoin storage, virtual cards, ACH and wire transfers, x402 and MPP calls, swaps and markets, with MCP, CLI, TypeScript SDK, and Python SDK access.

    official documentation · accessed Sep 3, 2026
  3. Sponge Gateway overview — paid API proxy and management surfaces

    The gateway documentation explains how a hosted proxy can expose upstream API routes through x402 or MPP with fixed, dynamic, or session pricing managed through a dashboard, MCP, or authenticated HTTP API.

    official documentation · accessed Sep 3, 2026
  4. Sponge Gateway concepts — payment modes and route-review boundary

    The concepts guide documents exact and usage-capped payments, upstream credential injection, resource ownership, and warns operators to review imported routes because an enabled route becomes callable by anyone who pays.

    official documentation · accessed Sep 3, 2026
  5. Sponge terms — beta status and third-party payment dependency

    The terms state that the service may be offered in beta and changed or discontinued, and identify a third-party payment-tokenization dependency.

    official legal · accessed Sep 3, 2026

Related tools

Comments