x402basequality 0.35

x402-gated HR document endpoint on Base, pay-per-request with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/hr/documents/35` is part of the lowpaymentfee.com platform, a collection of x402 protocol pay-per-call APIs spanning data analytics, AI/ML, finance, infrastructure, and more. The specific resource appears to serve an HR document (document ID 35) behind a paywall. Payment is settled on the Base network using USDC (contract `0x8335…2913`) via the x402 exact-payment scheme. The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). The endpoint accepts POST requests and returns `application/json`.

The broader lowpaymentfee.com platform advertises a uniform $0.02-per-request pricing model across all its endpoints, with no API keys, no rate limits, and no minimum commitments. However, the specific content and schema of the HR documents endpoint is not documented — there is no OpenAPI spec, no request/response schema, and no example payloads available from the crawled material. The endpoint is confirmed live via a valid 402 challenge response. Because the endpoint path suggests a single static document resource (document ID 35), it may return a fixed HR document rather than accepting query parameters, but this is speculative given the lack of documentation.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requesthr-document-retrievaljson-response

Use cases

  • Retrieving a specific HR document (ID 35) via a micropayment-gated API call
  • Demonstrating x402 protocol pay-per-request document access
  • Agent-driven document procurement settled in USDC on Base

Fit

Best for

  • Agents needing on-demand access to gated HR documents
  • Developers experimenting with x402 protocol micropayments
  • Use cases requiring no-signup, no-API-key document retrieval

Not for

  • Bulk document retrieval or batch processing (single document endpoint)
  • Users who need detailed API documentation or request/response schemas before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hr/documents/35 \
  -H "X-PAYMENT: <x402-payment-header>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, and pricing is clear ($0.02 per request in USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation of what the HR document contains or what POST body (if any) is expected, and the crawled pages beyond the homepage returned only 'Connect wallet' with no useful content. The endpoint path suggests a single static resource with unclear utility.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • No request body schema or response schema documented — unclear what POST body is expected
  • The endpoint path '/api/v1/hr/documents/35' references a specific document ID; unclear if other document IDs are available or what content is returned
  • The /api, /pricing, and /README pages returned no useful content beyond 'Connect wallet'
  • HR documents may contain sensitive or regulated personal data

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 21:23:46Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-23

Agent access