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/108/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com serves employee salary data for a specific employee record (ID 108). It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme.

The endpoint charges a maximum of 20,000 base units of USDC per request. Since USDC uses 6 decimals, that translates to $0.02 per call — consistent with the provider's site-wide flat pricing of $0.02/request. No API keys or rate limits are advertised; access is gated entirely by the x402 payment header. The provider hosts a broader catalog of endpoints spanning data analytics, AI/ML inference, finance/crypto feeds, and utility services, all at the same $0.02 price point.

Documentation is extremely thin. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no example payloads. The endpoint path suggests it returns salary information for employee 108, but the exact request body format and response structure are unknown. Treat this as a demonstration or early-stage endpoint until richer documentation appears.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-datasalary-lookuppay-per-requestjson-api

Use cases

  • —Retrieving salary information for a specific employee record via a single paid API call
  • —Demonstrating x402 payment-gated API access on the Base L2 network
  • —Integrating pay-per-request employee data into agent workflows without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents that need on-demand employee salary data without subscription commitments
  • —Projects requiring USDC-settled micropayment API access on Base

Not for

  • —Bulk payroll data retrieval across many employees (only one employee ID exposed)
  • —Production HR systems requiring authenticated, auditable access controls
  • —Users who need detailed API documentation or guaranteed SLAs

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the endpoint covers only a single hardcoded employee ID. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body format and response structure are unknown
  • —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content
  • —Endpoint path is hardcoded to employee ID 108; unclear if other employee IDs are supported
  • —Provider appears to be a demo or early-stage platform; reliability and data authenticity are unverified

Citations

Provenance

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

Agent access

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