x402basequality 0.35

Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 140) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint requires no API keys, no rate limits, and provides instant access — callers simply attach an x402 payment header to each request.

The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. This specific endpoint appears to serve structured JSON containing salary information for a given employee record. However, no OpenAPI schema, request body specification, or example response is documented, so the exact input parameters and response shape are unknown.

The endpoint is live and returns a valid x402 challenge (HTTP 402) with version 1 of the protocol. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC at contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base. The maximum payment timeout is 300 seconds.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-callno-api-keyjson-response

Use cases

  • Retrieving salary information for a specific employee record
  • Integrating employee compensation data into payroll or HR dashboards
  • Agent-driven lookups of salary data without pre-registration or API keys

Fit

Best for

  • Developers needing quick, keyless access to employee salary data
  • AI agents that can settle micropayments on Base via x402
  • Prototyping pay-per-call data integrations without subscription commitments

Not for

  • Bulk export of salary data across many employees (no batch endpoint documented)
  • Users who cannot settle USDC payments on the Base network
  • Production HR systems requiring documented schemas and SLAs

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documented request/response format, no example payloads, and the docs/pricing/README pages are all blank beyond a wallet-connect prompt. The purpose of this specific employee salary endpoint is only inferable from the URL path.

Warnings

  • No OpenAPI or request/response schema available — input parameters and response shape are unknown
  • Documentation pages (/docs, /pricing, /README) return no meaningful content
  • The endpoint path references a hardcoded employee ID (140); it is unclear if other IDs are supported or how to discover them
  • The broader site lists many API categories but none appear individually documented

Citations

Provenance

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

Agent access