PayPal payouts API endpoint paid per-call with USDC on Base via x402.
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/30` accepts POST requests and charges $0.02 per call in USDC on the Base network. Payment is handled inline — no API keys, no accounts, no rate limits. The caller includes an X-PAYMENT header with a signed USDC payment to the provider's address, and the endpoint processes the request upon verification.
The provider hosts a broader platform of pay-per-call APIs spanning data analytics, AI/ML inference, finance/crypto data, and utility services, all priced at $0.02 per request. However, the crawled documentation pages (docs, pricing, README) returned only a wallet-connect prompt with no substantive content, so details about request/response schemas, supported payout parameters, or error handling for this specific PayPal payouts endpoint are unavailable.
The endpoint is live and returns a valid x402 challenge (HTTP 402) with x402Version 1, accepting the "exact" payment scheme. The asset is USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, with a max amount of 20,000 base units ($0.02 given USDC's 6 decimals). Timeout is 300 seconds.
Capabilities
Use cases
- —Programmatically trigger PayPal payouts from an AI agent or automated workflow
- —Send PayPal payments without managing API keys or OAuth tokens
- —Integrate PayPal disbursements into a crypto-native application
Fit
Best for
- —Agents or bots that need to trigger PayPal payouts on demand
- —Developers wanting frictionless pay-per-call access to PayPal payouts
- —Crypto-native workflows that need fiat payout rails
Not for
- —High-volume bulk payouts where per-call pricing adds up significantly
- —Use cases requiring detailed PayPal payout status tracking or webhooks (no docs available)
- —Users who need comprehensive API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payouts/30 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schemas, supported parameters, or what the PayPal payout endpoint actually does in detail. All doc pages returned only a wallet-connect stub. The listing is effectively a stub.
Warnings
- —No request or response schema available — the endpoint's expected input body and output format are unknown.
- —Documentation pages (/docs, /pricing, /README, /api) all returned only a wallet-connect prompt with no content.
- —It is unclear what 'payouts/30' signifies (a $30 payout? a batch ID? a route parameter?).
- —PayPal payouts involve regulated financial activity — verify compliance and provider legitimacy before use.
- —The provider's broader API catalog lists many diverse endpoints (AI, analytics, finance, utils) all at $0.02 — the actual functionality behind each is unverified.
Citations
- —Endpoint returns HTTP 402 with x402Version 1 challenge, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/paypal/payouts/30
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/paypal/payouts/30
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —Documentation, pricing, and README pages returned only a wallet-connect prompt with no substantive content.https://lowpaymentfee.com/docs