x402basequality 0.25

Pay-per-call PayPal payments endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

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/10`) suggests it handles PayPal payment operations, though the exact request/response schema is not documented. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The provider, lowpaymentfee.com, hosts a broader catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely sparse: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail.

Because there is no OpenAPI schema, no request/response examples, and no documentation explaining what this PayPal payments endpoint actually does or what parameters it accepts, the practical utility for an agent is limited. The endpoint is confirmed live (returns a valid x402 402 challenge), but without knowing the expected POST body or the response format, callers would need to experiment or contact the provider.

Capabilities

x402-paymentusdc-settlementbase-networkpaypal-paymentspay-per-request

Use cases

  • Initiating or processing PayPal payments programmatically via a pay-per-call model
  • Integrating PayPal payment functionality into agent workflows without API key management
  • Making low-cost payment API calls settled in USDC on Base

Fit

Best for

  • Agents needing on-demand PayPal payment operations without subscription commitments
  • Developers experimenting with x402 protocol payment flows
  • Low-volume payment processing where $0.02/call is cost-effective

Not for

  • Production payment systems requiring documented, stable API contracts
  • High-volume payment processing where per-call fees add up
  • Use cases requiring detailed API documentation and guaranteed SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/10 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

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. Docs pages are empty. No OpenAPI schema. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or request/response schema provided; callers cannot know what POST body to send
  • The exact functionality of '/api/v1/paypal/payments/10' is unclear — the path suggests PayPal payment processing but nothing confirms this
  • No error handling, rate limit, or SLA information available

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 07:35:37Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access