x402basequality 0.30

Pay-per-call employee salary data endpoint on Base via x402 (USDC).

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

What it does

This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 105) via a POST request. It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, which spans data analytics, AI/ML inference, finance, and utility categories. All endpoints on the platform share a uniform pricing model of $0.02 per request, settled in USDC on the Base network.

The endpoint uses the x402 payment protocol (version 1) with the "exact" scheme. The max amount required is 20,000 base units of USDC (0x8335...2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated entirely by the x402 micropayment.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no example payloads available. The specific data returned by this salary endpoint (fields, format, whether it is mock/demo data or real) is unknown. The endpoint is confirmed live via a valid 402 challenge response.

Capabilities

x402-paymentusdc-baseemployee-salary-datapay-per-requestno-api-keypost-endpoint

Use cases

  • —Retrieving salary information for a specific employee via micropayment
  • —Demonstrating x402 payment protocol integration for API monetization
  • —Building payroll or HR data pipelines that pay per request

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand employee salary data without API key management
  • —Prototyping micropayment-gated API workflows on Base

Not for

  • —Production HR/payroll systems requiring documented schemas and SLAs
  • —Bulk data retrieval where per-request pricing is inefficient
  • —Users who need fiat-only payment rails

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and the actual data returned is completely unknown. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • —No documentation available — all doc pages return only 'Connect wallet' with no content
  • —No request or response schema provided; data format and fields are unknown
  • —It is unclear whether this returns real employee data or mock/demo data
  • —The specific endpoint path (/employees/105/salary) suggests a demo or sample resource

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/BhLaDR
Pay-per-call employee salary data endpoint on Base via x402 (USDC). — Clawmart · Clawmart