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/87`. 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 endpoint accepts POST requests and returns JSON. Payment is settled in USDC (contract `0x8335…2913` on Base) using the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted purely through per-request micropayment. The payment timeout is 300 seconds.
Documentation beyond the landing page is extremely sparse — the /docs, /api, /pricing, and /README pages all resolve to a minimal "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available. The specific behavior of the `/paypal/payments/87` resource (e.g., what PayPal payment data it returns or processes) is not documented anywhere in the crawled material. The endpoint is live and returning a valid x402 challenge, but the lack of documentation makes it difficult to know what to send or expect back.
Capabilities
Use cases
- —Programmatic access to PayPal payment data or operations via micropayment
- —Agent-driven payment workflows that settle per-call in USDC on Base
- —Integrating PayPal payment lookups into automated pipelines without API key management
Fit
Best for
- —Developers wanting keyless, pay-per-call access to payment-related endpoints
- —AI agents that can settle x402 micropayments on Base
- —Prototyping payment integrations without subscription commitments
Not for
- —Production use cases requiring well-documented request/response schemas
- —High-volume batch payment processing where per-call fees add up
- —Users who need detailed PayPal API parity (no documentation to confirm feature coverage)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/87 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the endpoint actually does, what request body it expects, or what it returns. No OpenAPI spec, no examples, and the docs pages are empty. The specific purpose of '/paypal/payments/87' is entirely unclear.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all return only a 'Connect wallet' prompt with no content
- —No OpenAPI or request/response schema provided; impossible to determine what this endpoint accepts or returns
- —The specific function of /api/v1/paypal/payments/87 is undocumented — the '87' path segment suggests a fixed resource ID but its meaning is unknown
- —Cannot verify whether this endpoint actually interacts with PayPal or is simply named that way
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/paypal/payments/87
- —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/87
- —Documentation pages (/docs, /api, /pricing, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs