x402basequality 0.35

x402-gated employee salary endpoint on Base, paid per-request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to employee salary data (specifically employee ID 126) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The endpoint charges a maximum of 20,000 base units of USDC per request. Since USDC uses 6 decimals, this equals $0.02 per call — consistent with the provider's site-wide flat pricing of $0.02/request. The provider advertises no API keys, no rate limits, and instant access; the only authentication is the x402 payment header.

The broader lowpaymentfee.com platform lists many other x402 endpoints spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all at the same $0.02 price point. However, this specific endpoint (/api/v1/employees/126/salary) is not listed on the provider's landing page among the advertised APIs, and no documentation describes what fields the salary response contains or what the POST body should look like. The endpoint is live (returns a valid 402 challenge), but the actual response schema and input parameters are unknown.

Capabilities

x402-paymentusdc-baseemployee-salary-dataper-request-pricingno-api-key

Use cases

  • Retrieving salary information for a specific employee via a pay-per-request model
  • Integrating employee compensation data into automated agent workflows
  • Demonstrating x402 micropayment protocol usage on Base network

Fit

Best for

  • Agents or services that need on-demand employee salary data without subscription commitments
  • Developers experimenting with x402 payment-gated APIs on Base
  • Scenarios requiring no-signup, no-API-key access to data endpoints

Not for

  • Bulk payroll data retrieval across many employees (only employee 126 is exposed at this path)
  • Use cases requiring well-documented input/output schemas before integration
  • Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but it is not listed among the provider's advertised APIs, has no documentation, no input/output schema, and the crawled docs/pricing/README pages are all blank beyond a 'Connect wallet' prompt. Effectively a stub with confirmed liveness.

Warnings

  • This specific endpoint (/api/v1/employees/126/salary) is not listed on the provider's landing page among advertised APIs — its purpose and legitimacy are unclear.
  • No input schema or output schema documentation is available; the POST body format is unknown.
  • All documentation pages (docs, api, pricing, README) returned only 'Connect wallet' with no useful content.
  • The endpoint appears to expose personal salary data — consider privacy and regulatory implications before use.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:47:53Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-25

Agent access