Pay-per-call PayPal payments endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a "Premium API Access" resource at the path `/api/v1/paypal/payments/27`. It is part of a broader platform offering dozens of pay-per-call API endpoints across categories like data analytics, AI/ML inference, finance, and infrastructure utilities — all gated by the x402 payment protocol on the Base network.
The specific endpoint accepts POST requests and is priced at 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. Payment is made via the x402 "exact" scheme, meaning callers attach a one-shot USDC payment in the X-PAYMENT header. No API keys or rate limits are advertised; access is instant once payment is included. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a max timeout of 300 seconds.
The endpoint's exact functionality under the "paypal/payments" path is not well-documented — the crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no further detail. The platform's landing page lists this endpoint's category implicitly under finance/payments, but no request/response schema, parameter documentation, or example payloads are available. Agents should treat this as a lightly-documented endpoint whose behavior must be discovered empirically.
Capabilities
Use cases
- —Programmatically triggering or querying PayPal payment operations via a crypto-gated API
- —Integrating PayPal payment flows into agent workflows without traditional API key management
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs on Base
- —Agents needing keyless, pay-per-call access to payment-related endpoints
- —Projects that want to avoid traditional API key provisioning for payment operations
Not for
- —Production PayPal integrations requiring well-documented, stable APIs with SLAs
- —Use cases needing detailed request/response schemas before integration
- —High-volume payment processing where $0.02/call overhead matters
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/27 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge), but there is essentially no documentation available — the docs, pricing, README, and API pages all render only a wallet-connect prompt. The purpose of the specific '/paypal/payments/27' path is unclear, no request/response schema is provided, and the endpoint's actual behavior is unknown beyond its x402 gating metadata.
Warnings
- —No request or response schema documented; actual endpoint behavior is unknown
- —All documentation pages (docs, pricing, README, api) returned only 'Connect wallet' with no content
- —The meaning of '/paypal/payments/27' is ambiguous — it is unclear whether this interacts with PayPal or is simply a naming convention
- —No examples, error codes, or rate limit information available
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/paypal/payments/27
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/paypal/payments/27
- —Documentation pages return only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs