clinkagent.com
Paid API · clinkagent.com · found in a public list · checked since 2026-10-26
Server error · latest check
Returns safety verdicts and risk flags for up to 25 token contracts.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Check a token before trading: Check a token address for rug-pull, honeypot, tax and holder-concentration risks.
GET https://clinkagent.com/token/verdict-batch$0.1 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 53 endpoints from clinkagent.com.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
1 passed, 1 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-26 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-26 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-26 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.1
- Protocols
- none seen yet
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 1 day tracked
Price from the registry's payment terms; protocols and networks as the registry states. Current terms first seen 2026-10-26; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 1
- Paid calls, 30 days
- 1
The registry's own figures, not our measurements.
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Calls it declares
GET addresses chain → chain requested counts tokens not_found
From the payment request it sent our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Financial and economic data / Crypto and on-chain data / Token, contract and wallet risk checks / Check a token before trading (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-27. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✓ says what it does; ✗ its latest check did not pass.
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Server error HTTP 503 expected 402 payment challenge |
— | 242 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 109 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_467eaa3e7e4c0fce