NFT collection floor-price endpoint, pay-per-call via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com returns the floor price for NFT collection #32. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled via the x402 protocol on the Base network using USDC.
The specific endpoint `/api/v1/collections/32/floor` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0.02 USD per request, since USDC uses 6 decimals). Payment is made inline via the X-PAYMENT header; no API keys, accounts, or rate limits are required. The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a 300-second timeout window.
Documentation beyond the landing page is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response format and the meaning of "collection 32" are unknown. The platform lists many other endpoints at $0.02 each across categories like sentiment analysis, text summarization, geocoding, and crypto gas estimates, but none have publicly documented schemas.
Capabilities
Use cases
- —Fetching the current floor price of a specific NFT collection
- —Monitoring NFT market conditions programmatically
- —Building trading bots or dashboards that need real-time floor prices
Fit
Best for
- —Agents needing on-demand NFT floor prices without API key management
- —Micropayment-based access to NFT market data
- —Quick, keyless integration for crypto-native applications
Not for
- —Bulk historical NFT data retrieval (no documented batch or historical endpoints)
- —Users who need detailed collection metadata beyond floor price
- —Anyone requiring comprehensive API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/collections/32/floor \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no examples, and no meaningful documentation. The purpose of 'collection 32' is undocumented. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README all return only a wallet-connect prompt
- —No request or response schema documented; actual payload format is unknown
- —The identity of 'collection 32' is not documented anywhere in the crawled material
- —The platform lists many endpoints but none appear to have public technical docs
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/collections/32/floor
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/collections/32/floor