NFT collection floor-price lookup via x402 micropayment on Base, $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns floor-price data for NFT collection ID 5. It is part of a broader suite of x402-gated APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3, and utility services. All endpoints share a uniform $0.02-per-request pricing model settled in USDC on the Base network.
The specific resource `/api/v1/collections/5/floor` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the provider's address on Base. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-call.
Documentation beyond the landing page is extremely thin. The /docs, /pricing, /api, and /README pages all resolve to a wallet-connect stub with no substantive content. There is no OpenAPI spec, no request/response schema, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data source, collection identifiers, and response format are undocumented.
Capabilities
Use cases
- —Querying the current floor price of a specific NFT collection programmatically
- —Building trading bots or dashboards that need real-time NFT floor data
- —Agents that need on-demand NFT valuation without managing API keys
Fit
Best for
- —Developers wanting key-less, pay-per-call NFT floor price data
- —AI agents with x402 payment capability on Base
- —Quick prototyping where subscription-free access matters
Not for
- —Production systems requiring documented response schemas and SLAs
- —Bulk historical NFT floor-price data retrieval
- —Users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/collections/5/floor \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what 'collection 5' refers to. No OpenAPI spec, no examples, and all doc pages are empty wallet-connect stubs. Pricing and payment details are clear, but the functional contract is entirely opaque.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all return empty wallet-connect pages
- —No request or response schema provided; callers must guess at the payload format
- —The collection identifier '5' is hardcoded in the URL with no explanation of what collection it maps to
- —The endpoint path suggests NFT collection data but the provider's landing page does not list this specific endpoint among its advertised APIs
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/collections/5/floor
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/collections/5/floor
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com