x402basequality 0.30

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/51/salary` returns salary information for employee ID 51, priced at $0.02 per request (20,000 base units of USDC on the Base network, where USDC uses 6 decimals). Payment is handled inline via the x402 protocol — no API keys, accounts, or rate limits are required.

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, crypto, and utility services, all at a uniform $0.02/request price point. The platform settles payments on the Base L2 network using USDC (contract 0x8335…2913). The x402 challenge confirms the endpoint is live and accepting payments with a 300-second timeout window.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary endpoint actually returns. The endpoint's purpose and response format must be inferred entirely from its URL path and the generic "Premium API Access" label.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-callno-api-keypost-method

Use cases

  • Retrieving salary information for a specific employee by ID
  • Integrating pay-per-call salary data into HR or payroll workflows
  • Agent-driven lookups of employee compensation without managing API keys

Fit

Best for

  • Developers needing on-demand employee salary data without subscription commitments
  • AI agents that can settle x402 payments on Base in USDC
  • Prototyping pay-per-call data access patterns with minimal setup

Not for

  • Bulk payroll data exports requiring thousands of records at once
  • Users who need detailed API documentation or response schema guarantees before integrating
  • Non-crypto users who cannot settle payments on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/51/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 (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and documentation pages are empty stubs. The actual data returned is unknown, making this effectively a stub listing.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or output schema provided; the response format for salary data is completely unknown.
  • The endpoint path suggests access to individual employee salary records, which may involve sensitive/regulated PII data — verify compliance requirements before use.
  • No request body schema documented; it is unclear what parameters (if any) the POST body should contain.

Citations

Provenance

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

Agent access