PayPal payouts endpoint via x402 micropayment on Base network, $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides a PayPal payouts API accessible via the x402 payment protocol. The specific path `/api/v1/paypal/payouts/80` suggests it triggers a PayPal payout operation, though the exact request/response schema is not documented in the available crawl material. Payment is settled in USDC on the Base network at $0.02 per call (20,000 base units with 6 decimals = $0.02), with no API keys, rate limits, or upfront commitments required.
The provider site (lowpaymentfee.com) hosts a broad catalog of x402-gated endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced uniformly at $0.02 per request. Documentation pages (/docs, /pricing, /api, /README) all resolve but render only a "Connect wallet" prompt, providing no further technical detail about request formats, parameters, or response structures. The x402 challenge is live and well-formed: it advertises x402 version 1, exact payment scheme, USDC asset (contract 0x8335…2913 on Base), and a 300-second payment timeout.
Because no OpenAPI spec, request schema, or response examples are available, the actual behavior of this endpoint — what parameters it expects, what a successful payout response looks like, and what PayPal integration it wraps — remains unclear. Agents should treat this as a stub listing until the provider publishes proper documentation.
Capabilities
Use cases
- —Triggering PayPal payouts programmatically without traditional API key management
- —Paying for PayPal payout services with USDC on Base via x402
- —Agent-initiated disbursements through PayPal
Fit
Best for
- —Developers wanting keyless, pay-per-use PayPal payout access
- —Crypto-native agents that can settle USDC on Base
- —Low-volume payout use cases where $0.02/request is economical
Not for
- —High-volume bulk PayPal payouts where traditional PayPal API with negotiated rates is cheaper
- —Users who need detailed documentation and SLAs before integrating
- —Non-crypto workflows that cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payouts/80 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request parameters, response format, or actual PayPal integration behavior. All doc pages render only 'Connect wallet'. No OpenAPI spec or examples exist. This is effectively a stub.
Warnings
- —No request or response schema available — endpoint behavior is entirely undocumented
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no technical content
- —The actual PayPal integration details (authentication, payout limits, supported currencies) are unknown
- —The '80' in the path is unexplained — it may be a fixed payout amount, an ID, or a parameter
Citations
- —x402 challenge returns 402 with USDC on Base, maxAmountRequired 20000 (=$0.02), payTo 0x1A2B…85F3https://lowpaymentfee.com/api/v1/paypal/payouts/80
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/paypal/payouts/80