x402basequality 0.30

x402-gated employee salary data endpoint on Base, pay-per-request with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to employee salary data (specifically employee ID 166) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).

The endpoint is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-gated APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, the specific endpoint being listed here (`/api/v1/employees/166/salary`) is not mentioned on the provider's landing page among the advertised API categories, which raises questions about its intended use and whether it returns real or demo data.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary response contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation makes it difficult to know what to expect from a successful paid request.

Capabilities

x402-paymentusdc-baseemployee-salary-datapay-per-requestjson-responsepost-method

Use cases

  • Retrieving salary information for a specific employee record
  • Demonstrating x402 micropayment integration with a data endpoint
  • Testing pay-per-request workflows on the Base network

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing on-demand salary data lookups
  • Prototyping micropayment-gated data access

Not for

  • Bulk payroll data exports (single-employee endpoint, no batch support documented)
  • Production HR systems requiring authenticated, auditable access
  • Users without USDC on Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — no schema, no examples, no description of response fields. The specific employee salary endpoint is not listed among the provider's advertised APIs, raising uncertainty about whether it serves real or demo data. Score reflects a stub-level listing.

Warnings

  • No documentation available — /docs, /api, /pricing, /README all return only a wallet-connect prompt
  • This specific endpoint (/api/v1/employees/166/salary) is not listed among the provider's advertised API categories
  • No request or response schema available; response structure is unknown
  • Unclear whether this returns real employee data, synthetic/demo data, or placeholder content
  • Hardcoded employee ID (166) in the URL — unclear if other IDs are supported

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:03:56Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access