x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/hr/documents/17

What it does

This endpoint at lowpaymentfee.com serves an HR document resource (document ID 17) behind an x402 paywall. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.

The specific endpoint `/api/v1/hr/documents/17` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 per request — consistent with the platform's uniform $0.02/request pricing. Payment is made via the x402 "exact" scheme directly to the provider's wallet. No API keys are required; access is granted immediately upon valid payment.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the HR document resource actually contains or what POST body it expects. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

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

Use cases

  • —Retrieving HR document data programmatically with per-request micropayments
  • —Integrating pay-as-you-go document access into agent workflows
  • —Accessing gated document resources without API key management

Fit

Best for

  • —Agents that need on-demand access to specific HR documents
  • —Developers exploring x402 pay-per-request patterns on Base
  • —Use cases where keyless, instant API access is preferred

Not for

  • —Users who need detailed API documentation or schema before integrating
  • —Bulk document retrieval where per-request fees would accumulate significantly
  • —Non-crypto workflows that cannot settle payments in USDC on Base

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/hr/documents/17
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no request/response examples, and no documentation describing what the HR document resource contains or what input the POST body expects. The docs pages are empty. This is effectively a stub listing.

Warnings

  • —No documentation available — all doc pages return only 'Connect wallet' with no content
  • —No OpenAPI or request/response schema provided
  • —Purpose of 'HR documents/17' resource is unknown — no description of what data is returned
  • —No example request body or response body available to guide integration

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/vr7GYd
x402-gated HR document endpoint on Base, pay-per-request with USDC. — Clawmart · Clawmart