x402basequality 0.35

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/127/salary` returns salary information for employee ID 127 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) at a cost of $0.02 per request.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. The x402 challenge confirms the endpoint is live and accepting payments.

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 it expects beyond a POST method. The endpoint path suggests it serves a specific employee record (ID 127), but it is unclear whether other employee IDs are available or how the broader employees API is structured.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-callno-api-keyjson-response

Use cases

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

Fit

Best for

  • Agents needing on-demand salary data with no subscription
  • Developers testing x402 payment flows on Base
  • Quick one-off salary lookups without account setup

Not for

  • Bulk employee data exports (single-record endpoint, no batch support documented)
  • Users who need detailed API documentation or OpenAPI specs before integrating
  • Non-crypto users who cannot settle payments in USDC on Base

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/127/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 (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and all documentation pages returned only a wallet-connect prompt. The specific purpose of the salary endpoint is only inferable from the URL path.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown.
  • All doc/pricing/README pages returned only 'Connect wallet' with no substantive content.
  • The endpoint path is for a single hardcoded employee ID (127); it is unclear if other IDs are supported.
  • The broader platform lists many API categories but none appear to include an 'employees' endpoint, raising questions about whether this is a demo or test resource.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:38:25Z · 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, settled in USDC. — Clawmart · Clawmart