# Yoofooz API Readiness Report

## API
**Name:** Sponge Wallet
**Docs URL:** https://docs.paysponge.com/wallet/sdk
**Domain:** docs.paysponge.com
**Generated At:** 2026-10-25T23:19:34.507310+00:00

## Certification
**Agent Readiness Score:** 65/100
**Certification Level:** Agent-Compatible With Gaps

## Agent Commerce Readiness
**Agent Commerce Score:** 35/100
**Agent Commerce Level:** Agent Commerce Emerging

This score is separate from the core Agent Readiness Score and evaluates MCP support, scoped agent identity, machine-native payments, consumption pricing, budget controls, rate controls, deterministic errors, auditability, least-privilege security, and agent observability.

## Category Scores
- Documentation Clarity: 10
- Machine Readable Spec: 10
- Authentication Clarity: 10
- Error Handling: 10
- Rate Limit Clarity: 0
- Agent Safe Workflow Support: 0
- Sandbox Availability: 10
- Webhook Event Support: 0
- Commercial Trust: 5
- Developer Experience: 10

## Strengths
- Documentation clarity
- Machine-readable specification (OpenAPI/GraphQL/etc.)
- Authentication model clarity
- Error handling and status codes
- Sandbox / test-mode availability
- Developer experience (SDKs, quickstart, CLI)

## Risks
- Rate-limit / quota behavior signal not detected in docs.
- Agent-safe workflow primitives (idempotency, retries) signal not detected in docs.
- Webhook / event support signal not detected in docs.
- Commercial trust (status, SLA, compliance) signal is partial; clearer documentation recommended.

## Recommended Next Steps
- Document rate limits, quota behavior, 429 responses, and Retry-After guidance.
- Document idempotency keys, test mode, dry runs, and safe retry semantics for agents.
- Expose webhook/event docs including event types, signature verification, and retry delivery.
- Strengthen: Publish status page, SLA, and security/compliance posture (SOC 2, GDPR, PCI as applicable).

## Evidence Signals

### Documentation clarity
- **Source:** https://docs.paysponge.com/api-reference/public-openapi.json
- **Matched:** parameters, request, response
- **Evidence:** "{ 'openapi': '3.0.3', 'info': , 'servers': [ ], 'components': { 'schemas': { 'cardbillingaddress': , 'cardshippingaddress': , 'storecreditcardrequest': , 'linkaddress': , 'linkpaymentmethodrequest': , 'linkpaymentcredentialrequest': , 'getcardrequest': , 'productlineitem': ,..."

- **Source:** https://docs.paysponge.com/wallet/sdk
- **Matched:** request, examples
- **Evidence:** "...swaps, and transaction history platform sdk : agent management, master keys, spending limits, and bank accounts payments and cards sdk : paid requests, x402, mpp, link, virtual cards, and sponge card sdk tools and helpers : mcp config, direct tools, httpclient , and publictoolsapi typescript..."

### Machine-readable specification (OpenAPI/GraphQL/etc.)
- **Source:** https://docs.paysponge.com/api-reference/public-openapi.json
- **Matched:** openapi, schema
- **Evidence:** "{ 'openapi': '3.0.3', 'info': , 'servers': [ ], 'components': { 'schemas': { 'cardbillingaddress': , 'cardshippingaddress': , 'storecreditcardrequest': ,..."

- **Source:** https://docs.paysponge.com/wallet/x402-payments
- **Matched:** endpoints
- **Evidence:** "pay x402 endpoints from an agent wallet. copy page copy page use x402 for http endpoints that return 402 payment required and accept a signed payment on retry. sdk..."

### Authentication model clarity
- **Source:** https://docs.paysponge.com/wallet/mcp
- **Matched:** oauth, authentication, authorization, api key, keys
- **Evidence:** "...to your agent framework. connect an mcp client use an agent api key ( sponge_live_... ) for cli-based clients. for app connectors that support oauth, connect the remote mcp url and authorize in the browser. mcp url: https://api.wallet.paysponge.com/mcp trading-only mcp url:..."

- **Source:** https://docs.paysponge.com/wallet/authentication
- **Matched:** oauth, api key, keys
- **Evidence:** "...copy page auth methods the sdk supports three ways to authenticate: 1. device flow (interactive) on first use, spongewallet.connect() starts the oauth device flow: 1 sdk requests a device code a code like abcd-1234 is displayed in your terminal and copied to clipboard. 2 browser opens you’re taken..."

### Error handling and status codes
- **Source:** https://docs.paysponge.com/wallet/mcp
- **Matched:** 400
- **Evidence:** "...) mcp = wallet.mcp() print (mcp.url) print (mcp.headers) <div class='size-6 rounded-md flex items-center justify-center shadow-xs text-gray-400 dark:text-white/50 dark:bg-background-dark dark:brightness-[1.35] dark:ring-1 dark :brightness-150 bg-white ring-1 ring-gray-400/30..."

- **Source:** https://docs.paysponge.com/wallet/x402-payments
- **Matched:** retry
- **Evidence:** "...x402 endpoints from an agent wallet. copy page copy page use x402 for http endpoints that return 402 payment required and accept a signed payment on retry. sdk typescript python import from '@paysponge/sdk' ; // connect as the paying agent. const wallet = await spongewallet . connect ( ); // fetch the..."

### Rate-limit / quota behavior
- **Source:** https://docs.paysponge.com/wallet/sdk
- **Matched:** limits
- **Evidence:** "...common next steps wallet sdk : addresses, balances, transfers, swaps, and transaction history platform sdk : agent management, master keys, spending limits, and bank accounts payments and cards sdk : paid requests, x402, mpp, link, virtual cards, and sponge card sdk tools and helpers : mcp config,..."

### Sandbox / test-mode availability
- **Source:** https://docs.paysponge.com/wallet/mcp
- **Matched:** test keys
- **Evidence:** "...server exposes get_balance , render_portfolio_ui , render_trade_ui , transfer , bridge , create_crypto_onramp , and a read-only hyperliquid . test keys hide create_crypto_onramp because crypto onramp links are mainnet-only. claude code run this command in your terminal: claude mcp add -s user http..."

### Commercial trust (status, SLA, compliance)
- **Source:** https://docs.paysponge.com/api-reference/public-openapi.json
- **Matched:** support, security
- **Evidence:** "{ 'openapi': '3.0.3', 'info': , 'servers': [ ], 'components': { 'schemas': { 'cardbillingaddress': , 'cardshippingaddress': , 'storecreditcardrequest': , 'linkaddress': , 'linkpaymentmethodrequest': , 'linkpaymentcredentialrequest': , 'getcardrequest': , 'productlineitem': , 'virtualcardshippingaddr..."

- **Source:** https://docs.paysponge.com/wallet/authentication
- **Matched:** support
- **Evidence:** "device flow, api keys, master keys, and credential storage. copy page copy page auth methods the sdk supports three ways to authenticate: 1. device flow (interactive) on first use, spongewallet.connect() starts the oauth device flow: 1 sdk requests a device..."

### Developer experience (SDKs, quickstart, CLI)
- **Source:** https://docs.paysponge.com/wallet/authentication
- **Matched:** sdk, cli
- **Evidence:** "device flow, api keys, master keys, and credential storage. copy page copy page auth methods the sdk supports three ways to authenticate: 1. device flow (interactive) on first use, spongewallet.connect() starts the oauth device flow: 1 sdk requests..."

- **Source:** https://docs.paysponge.com/wallet/sdk
- **Matched:** sdk, cli
- **Evidence:** "build with @paysponge/sdk and paysponge. copy page copy page install the sdk, connect a wallet, and call the methods you need. install typescript python npm install..."

## AI Analyst Summary
_Provider: nvidia | Model: nvidia/nemotron-3.5-super-vl-120b-a12b_

Sponge Wallet API is Agent-Compatible With Gaps at score 65, with strong documentation, specs, auth, errors, sandbox, and DX but missing rate-limit, idempotency, and webhook signals.

**Credibility Notes:**
- Agent readiness score: 65
- Certification level: Agent-Compatible With Gaps
- Partial commercial trust signal; clearer documentation recommended

**Next Actions:**
- Document rate limits, quota behavior, 429 responses, and Retry-After guidance.
- Document idempotency keys, test mode, dry runs, and safe retry semantics for agents.
- Expose webhook/event docs including event types, signature verification, and retry delivery.

## Yoofooz Summary
This API has been evaluated for autonomous AI-agent usability. The score reflects documentation quality, machine-readable specification signals, authentication clarity, error handling, workflow safety, commercial trust, and developer experience.