x402basequality 0.30

Pay-per-call employee salary data endpoint on Base via x402 (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/employees/182/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 182) via a POST request. Payment is settled on the Base network using USDC at a cost of $0.02 per request (20,000 base units with 6 decimals). The endpoint requires no API keys, no rate limits, and provides instant access — you simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services, all priced at $0.02 per request on the Base network. However, this specific listing covers only the `/api/v1/employees/182/salary` endpoint. Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response format and accepted request body fields are unknown.

Capabilities

x402-paymentusdc-baseemployee-salary-datapay-per-callno-api-key

Use cases

  • —Retrieving salary information for employee ID 182 via a single paid API call
  • —Integrating pay-per-call employee data into agent workflows without managing API keys
  • —Demonstrating x402 payment protocol usage on the Base network

Fit

Best for

  • —Agents needing on-demand employee salary data without subscription commitments
  • —Developers experimenting with x402 payment-gated APIs on Base
  • —Low-volume, pay-as-you-go data retrieval

Not for

  • —Bulk payroll data exports across many employees (only one employee ID exposed)
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 x402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the purpose of this specific employee salary endpoint is opaque. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are entirely unknown
  • —Docs, pricing, API, and README pages all render only 'Connect wallet' with no technical content
  • —This endpoint targets a single hardcoded employee ID (182); unclear if other employee IDs are available
  • —The provider's broader API catalog lists many endpoints but none are documented beyond titles and prices

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/ZMKK6N
Pay-per-call employee salary data endpoint on Base via x402 (USDC, $0.02/request). — Clawmart · Clawmart