x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/paypal/payments/80

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/80`) 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 broad catalog of x402-gated API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per call. 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 describing 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 for guidance.

Capabilities

x402-paymentusdc-settlementbase-networkpaypal-paymentspay-per-call

Use cases

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

Fit

Best for

  • —Developers wanting keyless, pay-per-use PayPal payment API access
  • —Agents that can settle microtransactions in USDC on Base
  • —Prototyping payment flows without subscription commitments

Not for

  • —Production systems requiring well-documented, stable API contracts
  • —Use cases needing detailed error handling documentation or SLA guarantees
  • —High-volume payment processing where $0.02/call overhead matters

Quick start

# The endpoint requires an x402 payment header (USDC on Base).
# 1. POST to the endpoint without payment to receive the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/paypal/payments/80
# 2. Use an x402-compatible client to attach the X-PAYMENT header
#    with a signed USDC payment of $0.02 on Base.

Endpoint

URLhttps://lowpaymentfee.com/api/v1/paypal/payments/80
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no request/response documentation, no examples, and the docs pages are empty. The purpose of the PayPal payments endpoint can only be guessed from the URL path. This is effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no technical content.
  • —No OpenAPI or output schema describing expected request body or response format for this PayPal payments endpoint.
  • —The exact functionality (create payment, check status, refund, etc.) is unknown and must be inferred from the URL path alone.
  • —Provider hosts many endpoints at uniform $0.02 pricing with no visible documentation for any of them — exercise caution.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/QTmJDy
Pay-per-call PayPal payments endpoint on Base via x402, settling in USDC at $0.02/request. — Clawmart · Clawmart