Sponge · Authentication Profile
Sponge Authentication
Authentication
Sponge's public Wallet API authenticates with a per-agent bearer API key. A browser device flow issues agent credentials interactively; agent keys are used non-interactively for servers/CI. Separately, an OAuth 2.0 / OIDC authorization server (S256 PKCE, dynamic client registration) fronts the hosted MCP servers for connectors that support OAuth.
Sponge secures its APIs with http, oauth2, and openIdConnect across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
CompanyAgent PaymentsAI AgentsWalletsCryptocurrencyPaymentsStablecoinsx402MPPFinancial InfrastructureMCPFintechCardsOnramp
Methods: http, oauth2, openIdConnect
Schemes: 4
OAuth flows: authorizationCode
API key in:
Security Schemes
bearerAuth http
DeviceFlow oauth2-device
OAuth2 oauth2
SIWE eip-4361