x402basequality 0.30

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 provides access to employee salary data via a simple POST request. The specific resource `/api/v1/employees/71/salary` returns salary information for employee ID 71, priced at $0.02 per request paid in USDC on the Base network. No API keys or accounts are required — payment is handled inline via the x402 protocol's X-PAYMENT header.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all uniformly priced at $0.02 per request. The platform advertises no rate limits, no minimums, and instant access.

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 detailed description of what fields the salary endpoint returns or what input parameters it accepts beyond the employee ID in the URL path. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual data quality and response format are unknown.

Capabilities

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

Use cases

  • Retrieving salary information for a specific employee by ID
  • Integrating pay-per-call salary data into HR or payroll workflows
  • Agent-driven lookups of employee compensation without pre-registration

Fit

Best for

  • Developers needing quick, keyless access to salary data via crypto micropayments
  • AI agents that can settle x402 payments on Base
  • Prototyping pay-per-use data access patterns

Not for

  • Bulk payroll data exports (single-employee endpoint, no batch support documented)
  • Users without USDC on Base network
  • Production HR systems requiring documented SLAs and schemas

Quick start

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

Endpoint

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 OpenAPI schema, no request/response examples, and all documentation pages are empty stubs. The actual data returned is completely unknown, making this effectively a stub listing.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README all return only a wallet connect prompt with no content.
  • No OpenAPI or schema describing request parameters or response format.
  • Unknown data source and accuracy for employee salary information.
  • The endpoint path references a specific employee ID (71); it is unclear whether other IDs are supported or what the data represents.
  • This endpoint may involve sensitive personal/employment data — verify compliance with applicable regulations.

Citations

Provenance

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

Agent access