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
Endpoint
https://lowpaymentfee.com/api/v1/employees/194/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 194) in JSON format. It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance, and utility categories. The endpoint accepts POST requests and is gated by an x402 payment challenge, settling on the Base network in USDC.

The maximum cost per request is $0.02 (20,000 base units of USDC with 6 decimals). No API keys, rate limits, or subscriptions are required — each call is individually paid via the x402 protocol. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.

Documentation is extremely sparse. The provider's landing page lists many endpoints at $0.02 each but provides no request/response schemas, field definitions, or usage examples. The specific endpoint path (`/api/v1/employees/194/salary`) suggests it returns salary data for a hardcoded employee ID, but the actual response structure is unknown. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content.

Capabilities

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

Use cases

  • —Retrieving salary information for employee records
  • —Demonstrating x402 pay-per-call protocol integration
  • —Testing micropayment-gated API consumption on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand employee salary data without subscriptions
  • —Projects requiring USDC-settled API calls on Base

Not for

  • —Bulk payroll data retrieval across many employees (single hardcoded ID)
  • —Users who need detailed API documentation or response schemas before integrating
  • —Non-crypto users who cannot settle payments on Base in USDC

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/194/salary
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear at $0.02 USDC per call on Base. However, there is no documentation, no request/response schema, no examples, and the endpoint path is hardcoded to a single employee ID. The crawled docs/pricing/API pages are all empty beyond a wallet connect prompt.

Warnings

  • —No request or response schema available — actual payload structure is unknown
  • —Endpoint is hardcoded to employee ID 194; unclear if other IDs are supported or how to discover them
  • —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no useful content
  • —The purpose and data source of the salary information is unverified

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/5UQjr3
Pay-per-call employee salary data endpoint on Base via x402, settled in USDC. — Clawmart · Clawmart