x402basequality 0.30

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 exposes an employee salary resource (`/api/v1/employees/134/salary`) 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services—all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific employee salary endpoint probed here does not appear in the site's public catalog, and no documentation, request schema, or response schema is available for it. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content.

Because there is no OpenAPI spec, no request/response examples, and no documentation describing what this endpoint actually returns or what inputs it expects, the practical utility for an agent is limited. The endpoint is confirmed live (402 challenge captured), but the lack of any schema or sample data means callers must discover the interface by trial and error.

Capabilities

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

Use cases

  • Retrieving salary information for a specific employee record
  • Demonstrating x402 payment-gated API access on Base
  • Integrating per-request crypto micropayments into data workflows

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that can settle USDC payments on Base L2
  • Use cases needing keyless, pay-per-call data access

Not for

  • Production payroll systems requiring documented, stable schemas
  • Users without a Base-compatible USDC wallet
  • Bulk data retrieval where per-request pricing is inefficient

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/134/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 challenge, but there is zero documentation, no OpenAPI spec, no request/response schema, and the endpoint path (employees/134/salary) does not appear in the provider's own catalog. Effectively a stub listing.

Warnings

  • No OpenAPI or schema available for this endpoint
  • No request or response examples documented anywhere
  • This specific endpoint (/api/v1/employees/134/salary) is not listed in the provider's public API catalog
  • All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
  • The nature of the returned salary data is completely unknown—could be mock/demo data

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:51:13Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-23

Agent access