x402basequality 0.30

Pay-per-call employee salary data endpoint on Base via x402, $0.02/request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

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

The endpoint uses the x402 payment protocol (version 1, "exact" scheme). When called without payment, it returns a 402 challenge specifying the USDC asset contract (0x8335…2913 on Base) and a maxAmountRequired of 20000 base units, which equals $0.02 (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by micropayment.

Documentation is extremely sparse. The provider's docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary response contains. The endpoint path suggests it returns salary information for employee 196, but the actual response structure is unknown.

Capabilities

x402-paymentusdc-basepay-per-callemployee-salary-datano-api-keymicropayment

Use cases

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

Fit

Best for

  • Developers wanting keyless, micropayment-gated API access
  • Agents that can settle x402 payments on Base in USDC
  • One-off or low-volume salary data lookups

Not for

  • Bulk employee data retrieval across many employees (only one employee ID exposed)
  • Users who need detailed API documentation or response schemas before integrating
  • Non-crypto users who cannot settle USDC payments on Base

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/196/salary
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to receive data.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the endpoint serves a single hardcoded employee ID with no explanation of the data model. Effectively a stub listing.

Warnings

  • No OpenAPI schema or response schema available — response structure is completely unknown
  • All documentation pages (docs, API, pricing, README) return only 'Connect wallet' with no content
  • Endpoint path is hardcoded to employee ID 196; unclear if other employee IDs are supported
  • No information on what 'salary' data fields are returned
  • Provider legitimacy and data source are unverifiable from available material

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:18:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access