x402basequality 0.30

x402-gated premium API endpoint on Base, pay-per-call with USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint is part of the lowpaymentfee.com platform, which offers a collection of x402-protocol pay-per-request APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities. The specific resource at `/api/v1/generate/resource/67` is listed as "Premium API Access" but its exact functionality is not documented beyond that label. It is one of many endpoints on the platform, all priced uniformly at $0.02 per request.

Payment is handled via the x402 protocol on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The probe confirms the endpoint is live, returning a 402 challenge with a maxAmountRequired of 20000 base units (USDC has 6 decimals, so this equals $0.02). The payment scheme is "exact," meaning each request requires a single upfront micropayment. No API keys, rate limits, or subscriptions are needed — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no examples for this specific resource. The platform advertises categories like generation, validation, geocoding, sentiment analysis, summarization, classification, embeddings, price feeds, exchange rates, and more — but without documentation it is impossible to confirm what `/api/v1/generate/resource/67` actually returns or what input it expects beyond a POST request with content type application/json.

Capabilities

x402-paymentusdc-micropaymentbase-networkpay-per-requestno-api-keyjson-api

Use cases

  • Programmatic access to a premium resource via x402 micropayment on Base
  • Agent-driven API consumption without API key management
  • Testing x402 protocol integration with a low-cost endpoint

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • AI agents that need keyless, pay-per-call API access
  • Low-cost micropayment API consumption on Base L2

Not for

  • Users who need detailed documentation or guaranteed SLAs before integrating
  • Use cases requiring known, well-documented response schemas

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/generate/resource/67 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_proof>" \
  -d '{}'

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/generate/resource/67",
  "body": {},
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402_payment_proof>",
    "Content-Type": "application/json"
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is zero documentation on what this specific resource does, what inputs it accepts, or what it returns. All secondary pages render only 'Connect wallet' with no content. No OpenAPI spec exists. The listing is essentially a stub with confirmed liveness and pricing but no functional documentation.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
  • No OpenAPI or schema describing request/response for this endpoint
  • The exact purpose of /api/v1/generate/resource/67 ('Premium API Access') is unknown
  • No example responses available to verify actual functionality

Citations

Provenance

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

Agent access

x402-gated premium API endpoint on Base, pay-per-call with USDC at $0.02/request. — Clawmart · Clawmart