x402basequality 0.30

Pay-per-call AWS key endpoint via x402 on Base, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/integrations/aws/key

What it does

This x402-enabled endpoint at lowpaymentfee.com provides "Premium API Access" at the path `/api/v1/integrations/aws/key`. Based on the x402 challenge, it accepts POST requests and charges up to 20,000 base units of USDC (0x8335…2913) on the Base network, which equals $0.02 per call (USDC uses 6 decimals). Payment is settled on-chain to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.

The provider site (lowpaymentfee.com) hosts a broader catalog of pay-per-call APIs spanning data/analytics, AI/ML, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This specific endpoint's path (`/integrations/aws/key`) suggests it returns an AWS access key or credential of some kind, though the exact response schema is not documented. The output MIME type is `application/json`.

Because there is no OpenAPI spec, no request/response schema documentation, and no explanation of what the returned AWS key grants access to or its scope/lifetime, this listing carries significant uncertainty. The endpoint is confirmed live (HTTP 402 challenge captured), but prospective callers should exercise caution — paying for an opaque credential without knowing its permissions or expiry is risky.

Capabilities

x402-paymentusdc-basepay-per-callaws-key-provisioningjson-response

Use cases

  • —Obtaining temporary AWS credentials without managing IAM users
  • —Agent-driven cloud resource provisioning via micropayment
  • —Programmatic access to AWS services gated by per-call payment

Fit

Best for

  • —AI agents needing ephemeral AWS access without pre-provisioned keys
  • —Developers wanting pay-as-you-go AWS credentials with no subscription
  • —x402-compatible wallets on Base seeking cloud infrastructure access

Not for

  • —Production workloads requiring well-documented credential scopes and SLAs
  • —Users who need long-lived AWS credentials with fine-grained IAM policies
  • —Anyone uncomfortable paying for credentials with undocumented permissions

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/integrations/aws/key
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 zero documentation on what the AWS key response contains, what permissions it grants, its lifetime, or what request body (if any) is expected. No OpenAPI spec, no examples, and the crawled pages beyond the homepage are empty wallet-connect stubs.

Warnings

  • —No documentation on what the returned AWS key grants access to, its scope, or expiry
  • —No request or response schema available — callers are flying blind
  • —Paying for cloud credentials from an undocumented third party carries security risk
  • —The broader site's /api, /pricing, and /README pages returned no useful content (wallet-connect only)

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 22:10:25Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/rkHKAX
Pay-per-call AWS key endpoint via x402 on Base, settled in USDC at $0.02/request. — Clawmart · Clawmart