Pay-per-call PayPal payments endpoint on Base via x402, $0.02/request in USDC.
What it does
This endpoint at lowpaymentfee.com provides a "Premium API Access" resource at the path `/api/v1/paypal/payments/11`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated via the x402 payment protocol on the Base network.
The specific endpoint accepts HTTP POST requests and charges 20,000 base units of USDC (contract `0x8335…2913` on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is made inline via the `X-PAYMENT` header; no API keys or accounts are required. The x402 challenge confirms the endpoint is live, returning a well-formed 402 response with version 1 of the protocol, a 300-second payment timeout, and an `exact` payment scheme.
Documentation on the site is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no explanation of what the PayPal payments endpoint actually returns or what input it expects beyond a POST body. The endpoint's name suggests it relates to PayPal payment processing, but without documentation this is speculative. Prospective callers should be aware that the actual functionality behind this endpoint is undocumented.
Capabilities
Use cases
- —Programmatic PayPal payment initiation or lookup via a single POST call
- —Agent-driven payment workflows that settle per-request in USDC on Base
- —Integrating low-cost payment API calls without API key management
Fit
Best for
- —Developers wanting keyless, pay-per-call payment endpoints
- —AI agents that can settle x402 micropayments on Base
- —Prototyping payment integrations without subscription commitments
Not for
- —Production payment processing requiring documented SLAs and schemas
- —Users who need detailed API documentation and error handling specs
- —High-volume batch payment operations where per-call pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/11 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the endpoint actually does, what inputs it expects, or what it returns. No OpenAPI spec, no examples, and all doc pages are empty. The listing is effectively a stub.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or request/response schema provided; actual endpoint behavior is unknown.
- —The endpoint name suggests PayPal payment functionality but this is unverified — no description of inputs or outputs exists.
- —The broader platform lists many endpoints but none appear documented beyond titles and prices.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/paypal/payments/11
- —The platform advertises $0.02 per 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/11
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs