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
Endpoint
https://lowpaymentfee.com/api/v1/employees/114/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to employee salary data via a simple POST request. The specific resource `/api/v1/employees/114/salary` returns salary information for employee ID 114 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) at a cost of $0.02 per request.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. The x402 challenge was successfully captured, confirming the endpoint is live and accepting payment-gated requests.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema, and no example payloads available. The endpoint's actual data content (what fields are returned for a salary lookup) must be inferred from the resource path alone. The employee ID 114 appears hardcoded in the URL, suggesting individual employee lookups are path-parameterized.

Capabilities

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

Use cases

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

Fit

Best for

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

Not for

  • —Bulk payroll data exports (single-employee endpoint, no batch mode documented)
  • —Users who cannot transact USDC on the Base network
  • —Production HR systems requiring authenticated, auditable access controls

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The x402 challenge is live and confirms pricing and network details, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no example payloads. The endpoint's actual data content is entirely unknown beyond what the URL path implies.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —All documentation pages (docs, API, pricing, README) returned only 'Connect wallet' with no content
  • —The employee ID 114 is hardcoded in the listed URL; it is unclear whether other IDs are valid or how to discover them
  • —No information on data provenance or whether this returns real or synthetic salary data

Citations

Provenance

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

Agent access

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