Pay-per-call PayPal payments endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a PayPal payments API accessible via the x402 payment protocol. The URL path (`/api/v1/paypal/payments/25`) suggests it handles PayPal payment operations, though the exact request/response schema is not documented in the available crawl material.
The endpoint is live and returns a valid x402 challenge. It accepts POST requests and settles payments on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). This is consistent with the site's advertised flat pricing of $0.02 per request across all endpoints. The provider advertises no API keys, no rate limits, and instant access.
The provider site (lowpaymentfee.com) hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/crypto data, and infrastructure utilities — all at the same $0.02/request price point. However, documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the actual input parameters, expected request body format, and response structure for this specific PayPal payments endpoint remain unknown.
Capabilities
Use cases
- —Programmatically initiate or process PayPal payments via a pay-per-call model
- —Integrate PayPal payment functionality into agent workflows without API key management
- —Access PayPal payment services settled on-chain via USDC on Base
Fit
Best for
- —Agents or bots needing on-demand PayPal payment operations without subscription commitments
- —Developers who prefer crypto-native pay-per-use billing over traditional API keys
- —Low-volume or bursty PayPal payment integrations where flat per-call pricing is economical
Not for
- —High-volume PayPal integrations where direct PayPal API access would be cheaper
- —Use cases requiring well-documented request/response schemas before integration
- —Production systems that need SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/25 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response format, or what the PayPal payments endpoint actually does. All doc pages return only 'Connect wallet' with no content. The listing is effectively a stub.
Warnings
- —No documentation available — all doc pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no substantive content
- —Request body schema and response format are completely unknown
- —The exact functionality of the PayPal payments endpoint (path param '25') is unclear — it could be a payment ID, amount, or category
- —Provider hosts a very broad catalog of disparate APIs (AI, finance, geocoding, PayPal) all at the same price, which may indicate a thin wrapper or placeholder service
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/paypal/payments/25
- —The site advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/paypal/payments/25
- —Documentation pages return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs