Discover / paycheck.hectichustle.workers.dev

Kertivo Shield

■ Challenge detected

Address-poisoning check before you send USDC on Base. Body {from, to} (or sender/recipient; chain=base, token=USDC only, others 400 not charged; optional contacts/known_addresses): scans the sender's recent Base USDC transfers for lookalikes (same first/last 4 hex) plus dust/zero-value transfers. No sender? {recipient, known_addresses} = offline contacts check; {address} alone scans its own history for poisoning signs. Returns risk low/medium/high, lookalikes, reasons, coverage.

Listed price
$0.001
Challenge detected
3 of the last 4 checks
Median response
188 ms
Last checked
16 Oct, 13:59 UTC
In our index since
11 Oct 2026

Endpoint

curl -i https://paycheck.hectichustle.workers.dev/address/check
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.
5 listed endpoints · on x402 Bazaar

Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.

Base URLhttps://paycheck.hectichustle.workers.dev

  • POST/address/check$0.001Address-poisoning check before you send USDC on Base. Body {from, to} (or sender/recipient; chain=base, token=USDC only, others 400 not charged; optional contacts/known_addresses): scans the sender's recent Base USDC transfers for lookalikes (same first/last 4 hex) plus dust/zero-value transfers. No sender? {recipient, known_addresses} = offline contacts check; {address} alone scans its own history for poisoning signs. Returns risk low/medium/high, lookalikes, reasons, coverage.
  • POST/trust/lookup$0.002Is this x402 API trustworthy? Body {url}. Returns its latest Kertivo Index endpoint trust score/grade (A, B, F, C-never-live, C-went-dark, or ungraded) and run date, plus evidence from a real paid test call: 402 status, price, payTo, settlement tx, on-chain check, HTTP status after paying, latency, schema and delivery result. Not in the index: status not_indexed. Also a public claims tally (buyer-filed disputed vs delivered), kept separate from the grade. Free grade-only: GET /trust/lookup?url=
  • POST/address/check/full$0.005Full-history address-poisoning check before you send USDC on Base. Same risk/lookalike/seenBefore logic as /address/check, but funding history comes from ONE Blockscout index call (x402, up to the sender's 500 most recent Base USDC transfers; v2 page fallback) so coverage is usually the sender's full Base USDC history. Body {from, to}. Not charged if the index is down. Cheap partial/RPC tier: POST /address/check ($0.001).
  • POST/check$0.01Payment verification for x402: verify a USDC transaction on Base — did this payment really settle, and did it pay the right address the right amount? Send a tx hash (or x402 authorization): confirmations, real-USDC transfer check, expectedPayTo/expectedAmount match, fake-USDC and lookalike-address warnings, who funded the payer (external, self_funded, unknown), plain-English summary and a receipt. Body {txHash|authorization, expectedPayTo?, expectedAmount?}. Free demo: POST /demo.
  • POST/check/deep$0.05Did this USDC payment settle, and who funded this wallet (the payer)? Deep Base verification: confirmations, payTo/amount match, fake-token and lookalike warnings, plus the payer's FULL inbound USDC history (no window), top funders, coverage stats and a recheckable sha256 receipt. Not charged if the index is down. Body {txHash, expectedPayTo?, expectedAmount?}.

A dash means the listing gives no price or method. Copy buttons copy the full URL.

Showing 5 of 5 listed endpoints.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/paycheck.hectichustle.workers.dev

Recent checks

11 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.16 Oct 2026
All 4 checks
When (UTC)ResultHTTPResponse
16 Oct, 13:59 UTCChallenge detected402279ms
15 Oct, 08:20 UTCChallenge detected402188ms
13 Oct, 20:45 UTCChallenge detected40266ms
11 Oct, 12:57 UTCNo challenge detected40490ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 16 Oct, 13:59 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What price is recorded for Kertivo Shield?

Its listed price is $0.001.

What payment terms does Kertivo Shield advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is Kertivo Shield listed?

In x402 Bazaar. Superstables first indexed it on 11 Oct 2026.

Something wrong on this page? Tell us.