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/78`. 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 via the x402 payment protocol on the Base network.
The specific endpoint accepts POST requests and is priced at a maximum of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is made via an `X-PAYMENT` header using the x402 "exact" scheme, settling directly to the provider's wallet. No API keys or accounts are required; access is granted immediately upon valid payment. The platform advertises no rate limits and no minimum commitments.
Documentation beyond the landing page is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the PayPal payments endpoint actually returns. The endpoint name suggests it may proxy or wrap PayPal payment functionality, but this is unconfirmed. Prospective users should test the endpoint to understand its actual behavior before relying on it in production.
Capabilities
Use cases
- —Making PayPal-related payment calls without traditional API key registration
- —Integrating PayPal payment functionality into agent workflows via x402 micropayments
- —Programmatic access to payment processing with per-call USDC settlement
Fit
Best for
- —Agents or bots that need on-demand payment API access without account signup
- —Developers experimenting with x402-gated financial endpoints
- —Low-volume, pay-as-you-go PayPal payment integrations
Not for
- —High-volume production payment processing requiring SLAs and documentation
- —Users who need detailed API documentation and response schemas before integration
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/78 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge) and pricing is clear at $0.02/request in USDC on Base. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and no examples. The actual functionality of the 'paypal/payments/78' endpoint is entirely opaque — it could be a stub or a real proxy. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet' with no content
- —No OpenAPI or schema definition; request body format and response structure are completely unknown
- —The endpoint path '/api/v1/paypal/payments/78' suggests PayPal integration but this is unverified — actual behavior is opaque
- —The hardcoded '/78' in the path is unexplained and may indicate a specific resource ID rather than a general-purpose endpoint
Citations
- —Endpoint returns x402 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/paypal/payments/78
- —Platform advertises $0.02/request pricing 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/78