x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 74) via a POST request. It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance, and utility categories. The endpoint settles payments on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme.

The maximum amount required per call is 20,000 base units of USDC. Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the provider's advertised flat pricing of $0.02/request across all endpoints. No API keys or rate limits are advertised; access is granted immediately upon valid x402 payment. The payment timeout is 300 seconds.

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 schema, no request/response examples, and no description of what fields the salary response contains or what input the POST body expects. The endpoint is live (returns a proper 402 challenge), but the actual data returned after payment is unknown.

Capabilities

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

Use cases

  • Retrieving salary information for employee records
  • Integrating employee compensation data into payroll or HR workflows
  • Agent-driven lookups of salary data with automatic USDC micropayments

Fit

Best for

  • Agents needing on-demand employee salary data without API key management
  • Developers experimenting with x402 pay-per-call patterns on Base
  • Low-volume, ad-hoc salary data lookups

Not for

  • Bulk payroll data exports (single-employee endpoint, no batch support evident)
  • Users without USDC on Base network
  • Anyone needing detailed documentation or guaranteed schema stability

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and the actual data returned is completely unknown. The endpoint path is hardcoded to a single employee ID (74), raising questions about generality.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README all render only a wallet-connect prompt with no content.
  • No OpenAPI or request/response schema provided; input body format and response fields are unknown.
  • Endpoint path is hardcoded to employee ID 74; unclear if other employee IDs are supported or how to discover them.
  • The nature and source of the 'salary' data is unspecified — could be mock/demo data.

Citations

Provenance

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

Agent access

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