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/199/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 199) 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 use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint `/api/v1/employees/199/salary` costs $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled via the x402 `X-PAYMENT` header with the "exact" scheme. The platform advertises no API keys, no rate limits, and instant access — you simply attach a valid x402 payment header to each call.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned 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 endpoint returns or what input it expects beyond the HTTP POST method. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data payload and its structure are unknown.

Capabilities

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

Use cases

  • —Retrieving salary information for a specific employee on demand
  • —Integrating pay-per-call salary data into HR or payroll workflows
  • —Agent-driven lookups of compensation data without API key management

Fit

Best for

  • —Agents needing on-demand salary data with no subscription or API key
  • —Developers experimenting with x402 payment-gated APIs
  • —Low-volume, pay-as-you-go data retrieval

Not for

  • —Bulk employee data exports (single-employee endpoint, no batch support evident)
  • —Users who need detailed API documentation or response schema guarantees
  • —Production systems requiring SLA or uptime guarantees (no docs or terms available)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI schema, no documentation, no request/response examples, and no explanation of what data is returned. The crawled pages beyond the landing page were all empty ("Connect wallet" only). This is effectively a stub listing.

Warnings

  • —No API documentation available — all doc pages return only a wallet connect prompt
  • —No request body schema or response schema provided; data structure is entirely unknown
  • —The endpoint path suggests demo/sample data (employee ID 199) rather than a production data source
  • —No terms of service, privacy policy, or SLA information found

Citations

Provenance

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

Agent access

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