PayPal payouts endpoint paid per-call via x402 on Base (USDC), $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a PayPal payouts API accessible via the x402 payment protocol. The endpoint path `/api/v1/paypal/payouts/90` suggests it triggers a PayPal payout operation. Each call costs $0.02 in USDC on the Base network — the x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys or rate limits are required; payment is handled inline via the x402 `X-PAYMENT` header.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per request and settled in USDC on Base. Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The specific behavior of this PayPal payouts endpoint (required input fields, response format, what "90" in the path signifies) is not documented anywhere in the crawled material.
The endpoint is live and returns a valid x402 challenge (HTTP 402) when called without payment. However, the lack of documentation means callers must experiment or contact the provider to understand the expected POST body and response structure.
Capabilities
Use cases
- —Triggering PayPal payouts programmatically without managing API keys
- —Automating disbursements or payments to PayPal recipients via a pay-per-call model
- —Agent-initiated PayPal transfers settled with USDC on Base
Fit
Best for
- —Developers wanting PayPal payout access without a PayPal developer account
- —AI agents that need to trigger PayPal payments using crypto micropayments
- —One-off or low-volume PayPal payouts without subscription commitments
Not for
- —High-volume PayPal payout operations where direct PayPal API integration is cheaper
- —Use cases requiring detailed documentation, SLAs, or guaranteed uptime
- —Scenarios needing non-USDC or non-Base payment settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payouts/90 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is live (valid x402 402 challenge), but there is zero documentation on request/response schema, no OpenAPI spec, and the docs pages are empty. The purpose of the endpoint (PayPal payouts) is inferred solely from the URL path. This is effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —No request or response schema is documented; the expected POST body is unknown.
- —The meaning of '90' in the endpoint path is unclear — it may be a payout amount, an ID, or a parameter.
- —The actual functionality (whether this truly triggers PayPal payouts) cannot be verified from available material.
- —Provider hosts many diverse endpoints at $0.02 each with no documentation — exercise caution.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/paypal/payouts/90
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/paypal/payouts/90
- —Docs, pricing, API, and README pages render only 'Connect wallet'https://lowpaymentfee.com/docs