x402basequality 0.35

Portfolio performance data via x402 micropayment on Base network for $0.02/request

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/portfolios/87/performance

What it does

This endpoint at lowpaymentfee.com provides portfolio performance data for a specific portfolio (ID 87) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) at a cost of $0.02 per request (maxAmountRequired of 20,000 base units with 6 decimals). No API keys or rate limits are required — access is granted per-call via the x402 payment protocol.

The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced uniformly at $0.02 per request. This specific endpoint falls under the finance category and appears to return performance metrics for a pre-defined portfolio. However, the exact response schema, available fields, and what "portfolio 87" represents are not documented in any crawled material.

The endpoint is confirmed live: it returns a valid x402 version-1 challenge with a 402 status code. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so details about request parameters, response format, and portfolio semantics remain unknown.

Capabilities

x402-paymentportfolio-performanceusdc-base-networkpay-per-calljson-responseno-api-key

Use cases

  • —Retrieving performance metrics for portfolio 87 via automated agents
  • —Integrating portfolio performance data into dashboards without API key management
  • —Pay-per-call access to financial portfolio data on Base network

Fit

Best for

  • —Agents needing on-demand portfolio performance data without subscriptions
  • —Developers prototyping finance dashboards with low per-call costs
  • —x402-compatible clients on the Base network

Not for

  • —Users needing documented response schemas before integration
  • —Bulk historical portfolio analysis requiring high-volume batch access
  • —Accessing arbitrary portfolio IDs (endpoint is fixed to portfolio 87)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/portfolios/87/performance \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-header>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/portfolios/87/performance
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 challenge, but there is no documentation on request parameters, response schema, or what portfolio 87 represents. All doc pages returned empty 'Connect wallet' stubs. Pricing and payment details are clear, but the functional contract is opaque.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all return only 'Connect wallet' with no content
  • —Response schema and request body format are completely undocumented
  • —The endpoint is hardcoded to portfolio ID 87 with no explanation of what this portfolio contains
  • —No OpenAPI spec or AI plugin manifest found

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/fQgdVr
Portfolio performance data via x402 micropayment on Base network for $0.02/request — Clawmart · Clawmart