x402basequality 0.30

x402-gated product inventory endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/products/34/inventory

What it does

This endpoint at lowpaymentfee.com provides access to a product inventory resource (product ID 34) via the x402 payment protocol. It is one of many endpoints offered by the lowpaymentfee.com platform, which hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 protocol to gate access, settling payments in USDC on the Base network.

The specific endpoint `/api/v1/products/34/inventory` accepts POST requests and returns JSON. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD per request, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.

Documentation on the site is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the inventory data actually contains or what fields the POST body expects. The endpoint is confirmed live (returns 402 with a valid x402 challenge), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

x402-paymentusdc-settlementbase-networkproduct-inventorypay-per-requestno-api-keyjson-response

Use cases

  • —Querying product inventory data for product ID 34 on a per-request payment basis
  • —Integrating pay-per-call inventory checks into automated agent workflows
  • —Accessing inventory information without needing API key registration

Fit

Best for

  • —Agents or services that need on-demand inventory lookups with crypto micropayments
  • —Developers experimenting with x402 protocol integrations
  • —Use cases where avoiding API key management is desirable

Not for

  • —Production systems requiring well-documented request/response schemas
  • —High-volume inventory queries where per-request pricing may add up
  • —Users who cannot transact in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/products/34/inventory \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/products/34/inventory
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, no description of what inventory data is returned or what POST body is expected. The listing is effectively a stub.

Warnings

  • —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content
  • —No OpenAPI or request/response schema provided; request body format and response structure are unknown
  • —The specific purpose and data returned by the /products/34/inventory endpoint is undocumented
  • —The broader lowpaymentfee.com platform lists many endpoints but provides no detailed docs for any of them

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 23:03:42Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/NefEk4
x402-gated product inventory endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart