x402basequality 0.30

PayPal payouts endpoint via x402 micropayment on Base network for $0.02/request

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a PayPal payouts API accessible via the x402 payment protocol. The specific route `/api/v1/paypal/payouts/97` is labeled "Premium API Access" and accepts POST requests. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with USDC's 6 decimals = $0.02). No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/crypto data, and infrastructure utilities — all priced at $0.02 per request on the same x402 model. However, the specific functionality behind this particular PayPal payouts endpoint is not documented in the crawled material. The endpoint path suggests it triggers or retrieves information about a PayPal payout (resource ID 97), but no request/response schema, parameter documentation, or usage examples were found.

The endpoint is confirmed live: it returns a well-formed x402 version 1 challenge with a 402 status code. The USDC asset contract (0x8335…2913) matches the canonical Base mainnet USDC address. The payment recipient is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. Without documentation on what the endpoint actually returns or what POST body it expects, agents should treat this as an opaque paid endpoint until further docs are available.

Capabilities

x402-paymentpaypal-payoutsusdc-basepay-per-callno-api-keypost-endpoint

Use cases

  • Triggering or querying PayPal payouts programmatically via a pay-per-call model
  • Integrating PayPal disbursements into agent workflows without managing API keys
  • Making one-off payout requests settled with USDC on Base

Fit

Best for

  • Agents needing PayPal payout functionality without subscription commitments
  • Developers who prefer crypto-settled micropayments over traditional billing
  • Low-volume or sporadic PayPal payout use cases

Not for

  • High-volume PayPal payout operations where direct PayPal API integration is cheaper
  • Use cases requiring detailed documentation or SLA guarantees
  • Users without access to USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/paypal/payouts/97 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-proof>" \
  -d '{}'

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what the PayPal payouts endpoint actually does. The crawled pages beyond the homepage only show 'Connect wallet' with no substantive content. This is effectively a stub listing.

Warnings

  • No documentation found for this specific endpoint — request body and response schema are unknown
  • The endpoint path includes a numeric ID (97) whose meaning is unexplained
  • Docs, API, pricing, and README pages all returned only 'Connect wallet' with no useful content
  • Actual PayPal payout behavior is entirely inferred from the URL path; no confirmation of functionality exists

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 08:05:42Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

PayPal payouts endpoint via x402 micropayment on Base network for $0.02/request — Clawmart · Clawmart