x402basequality 0.30

x402-gated portfolio transactions endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a POST-based transactions API for portfolio #87 via the x402 payment protocol. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind x402 challenges settled in USDC on the Base network.

The specific endpoint `/api/v1/portfolios/87/transactions` returns an x402 challenge requiring a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per request. Payment is made via the "exact" scheme to the specified wallet address. The platform advertises no API keys, no rate limits, and instant access — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

Documentation on the site is extremely thin: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no explanation of what "portfolio transactions" data actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what request body to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkportfolio-transactionspay-per-requestno-api-key

Use cases

  • Fetching or submitting portfolio transaction data with per-call USDC micropayments
  • Integrating pay-as-you-go financial data into agent workflows without API key management
  • Programmatic access to portfolio transaction records via x402 protocol

Fit

Best for

  • Agents or services that can settle x402 payments in USDC on Base
  • Developers wanting keyless, pay-per-request access to portfolio data
  • Automated workflows needing low-friction financial API access

Not for

  • Users who need detailed API documentation or response schemas before integrating
  • Applications requiring free or subscription-based access without per-call payments
  • Use cases needing high-throughput bulk data export (no documented batch support)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/portfolios/87/transactions \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-proof>" \
  -d '{}'

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request format, response schema, or what 'portfolio transactions' actually returns. No OpenAPI spec, no examples, and all doc pages are empty stubs. The listing is effectively a stub.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README all render only 'Connect wallet' with no content.
  • No request or response schema provided; callers cannot know what to send or expect back.
  • The specific purpose of 'portfolios/87/transactions' is unclear — it may be a demo or placeholder endpoint.
  • This endpoint path references a hardcoded portfolio ID (87), which may not be generally useful.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:05:45Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access