x402basequality 0.35

x402-gated transaction receipt endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/transactions/260/receipt

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 260) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no commitments.

The specific endpoint probed (/api/v1/transactions/260/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme. The endpoint accepts POST requests and returns application/json.

Documentation 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 spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform appears functional (root returns 200, x402 challenge is well-formed), but the lack of documentation makes it difficult to know what data is returned or what input the POST body expects.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-requestno-api-keyjson-response

Use cases

  • —Retrieving transaction receipt data for transaction ID 260 via a single micropayment
  • —Programmatic access to receipt information without API key registration
  • —Agent-driven workflows that need to fetch financial transaction records on-demand

Fit

Best for

  • —Developers wanting zero-signup, pay-per-use API access
  • —AI agents that can settle x402 payments in USDC on Base
  • —Use cases requiring transaction receipt retrieval without subscription overhead

Not for

  • —Users needing detailed API documentation or OpenAPI specs before integrating
  • —Bulk retrieval of many transaction receipts (each call costs $0.02 individually)
  • —Non-crypto users who cannot settle payments in USDC on Base

Quick start

# 1. POST to the endpoint without payment to get the x402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/transactions/260/receipt
# Returns 402 with x402 payment challenge in JSON body.
# 2. Construct an X-PAYMENT header per x402 spec, paying 20000 base units USDC ($0.02) on Base.
# 3. Re-send the POST with the X-PAYMENT header to receive the receipt.

Example

Response

{
  "error": "X-PAYMENT header is required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "https://lowpaymentfee.com/api/v1/transactions/260/receipt",
      "description": "Premium API Access",
      "maxAmountRequired": "20000",
      "maxTimeoutSeconds": 300
    }
  ],
  "x402Version": 1
}

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/260/receipt
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is well-formed and the endpoint is live, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples of the actual receipt payload. The docs pages are empty stubs. The specific purpose of this particular receipt endpoint is unclear beyond the generic 'Premium API Access' label.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
  • —No OpenAPI or schema definition for request body or response payload
  • —Unclear what data the transaction receipt for ID 260 actually contains
  • —The broader platform lists many endpoints but none have documented schemas

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 12:47:39Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/M6afBD