x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/employees/70/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 70) 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 no upfront commitments — callers simply attach an x402 payment header with each request.

The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/employees/70/salary` endpoint. The x402 challenge confirms the endpoint is live, accepting POST requests, and returning application/json responses.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary response contains or what input the POST body expects. The endpoint path suggests it returns salary data for employee ID 70, but the actual schema and semantics are unknown.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-callno-api-key

Use cases

  • —Retrieving salary information for a specific employee record
  • —Demonstrating x402 payment protocol integration with a simple data endpoint
  • —Building payroll or HR dashboards that pull salary data on demand

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand employee salary data without API key management
  • —Low-volume, pay-as-you-go data retrieval

Not for

  • —Bulk payroll data exports across many employees (only one employee ID exposed)
  • —Use cases requiring detailed documentation or guaranteed SLAs
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/70/salary
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and no meaningful documentation beyond a wallet-connect prompt. The endpoint path is narrow (single employee ID), and the actual data returned is unknown.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are entirely unknown
  • —All documentation pages (docs, API, pricing, README) render only a 'Connect wallet' prompt with no technical content
  • —Endpoint is scoped to a single employee ID (70); unclear if other employee IDs are supported or if this is a demo
  • —The purpose and legitimacy of 'employee salary data' sold publicly for $0.02 is unclear — may be synthetic/demo data

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/nqBdJJ
Pay-per-call employee salary data endpoint on Base via x402, settled in USDC. — Clawmart · Clawmart