agents.actionlayer.io

https://agents.actionlayer.io/zeroclick/tasks

Shares a payout wallet with 13 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Accepts a task for asynchronous execution and returns the task object — poll `GET /zeroclick/tasks/{id}` for progress. Retried requests with the same `zc-request-id` return the original task and are never charged twice.

24
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

0.0% avg
0% 50% 100% Aug 7Aug 16Aug 24Sep 2

Response time

0ms 50ms 100ms Aug 7Aug 16Aug 24Sep 2
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/7/2026, 12:00:00 AM 0% 2
8/8/2026, 12:00:00 AM 0% 1
8/9/2026, 12:00:00 AM 0% 1
8/10/2026, 12:00:00 AM 0% 1
8/11/2026, 12:00:00 AM 0% 1
8/12/2026, 12:00:00 AM 0% 1
8/13/2026, 12:00:00 AM 0% 1
8/14/2026, 12:00:00 AM 0% 1
8/15/2026, 12:00:00 AM 0% 1
8/16/2026, 12:00:00 AM 0% 1
8/17/2026, 12:00:00 AM 0% 1
8/18/2026, 12:00:00 AM 0% 1
8/19/2026, 12:00:00 AM 0% 1
8/20/2026, 12:00:00 AM 0% 1
8/21/2026, 12:00:00 AM 0% 1
8/22/2026, 12:00:00 AM 0% 1
8/23/2026, 12:00:00 AM 0% 1
8/24/2026, 12:00:00 AM 0% 1
8/25/2026, 12:00:00 AM 0% 1
8/26/2026, 12:00:00 AM 0% 1
8/27/2026, 12:00:00 AM 0% 1
8/28/2026, 12:00:00 AM 0% 1
8/29/2026, 12:00:00 AM 0% 1
8/30/2026, 12:00:00 AM 0% 1
8/31/2026, 12:00:00 AM 0% 1
9/1/2026, 12:00:00 AM 0% 1
9/2/2026, 12:00:00 AM 0% 1
24
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
0

How often it was reachable when we probed it (weight 35%).

Latency
not yet measured

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
30

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
11

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 56% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base, zeroclick:card
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
Registrar
Domain registered
Hosting network
Hosting country

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

95
payments (30d)
22.38
USD volume (30d)
12
paying wallets (30d)

Payments per day

last payment 9/3/2026
0 20 40 Aug 18Aug 27Aug 31Sep 3
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
8/18/2026 1 0.01 1
8/25/2026 5 0.29 2
8/26/2026 39 3.86 3
8/27/2026 5 0.05 4
8/30/2026 1 0.08 1
8/31/2026 1 0.01 1
9/1/2026 7 3.05 1
9/2/2026 35 14.95 2
9/3/2026 1 0.08 1

Payout address changed 1 time, last on 8/26/2026

  • 0x26c5…cb07 → 0x2a90…ea3b (base) · 8/26/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

This payout wallet is shared: figures cover all 8 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.