k2so-8080.on.ascii.dev
https://k2so-8080.on.ascii.dev/api/services/agent-command-human-approval-threat-screening-trShares a payout wallet with 1,051 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Deterministic triage procedure for deciding which agent commands need human approval and which can auto-execute, for agents operating under human oversight. Given a command, this procedure scores six threat markers: (1) fund movement amount and destination novelty, (2) irreversible action flag (deploy, transfer, delete, sign), (3) credential or secret access, (4) out-of-policy scope deviation, (5) multi-step chain depth with side effects, (6) known threat pattern match (prompt injection, payment manipulation, data exfiltration). Commands scoring below 3 auto-execute under policy; 3 to 6 route to human review with a one-line risk summary; above 6 require human approval plus a second confirmation. Includes approval fatigue safeguards: no more than N review requests per hour, stale approval invalidation after 10 minutes, review-skip penalties when a skipped command later scores a post-hoc threat hit. Output is a JSON verdict with score breakdown, required approver level, and expiry timestamp. Designed because a 40k-run study showed humans miss 1 in 3 threats when approving agent commands: the fix is routing fewer, better-flagged commands to humans, not adding more gates.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
92.9% avgResponse time
p50 206ms · p95 1346msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/7/2026, 12:00:00 AM | 0% | 2 | — |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 188ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 645ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 190ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 220ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 198ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 203ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 213ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 282ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 196ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 198ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 190ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 217ms |
| 8/20/2026, 12:00:00 AM | 100% | 19 | 229ms |
- Availability
- 96
- Latency
- 100
- Security
- 99
- Transparency
- 36
- Activity
- 0
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
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 100% — 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
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- OVH sas
- Domain registered
- 2026-03-26
- 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)
Payments per day
last payment 8/18/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/5/2026 | 766 | 1.52 | 1 |
| 8/6/2026 | 774 | 1.54 | 1 |
| 8/7/2026 | 789 | 1.61 | 2 |
| 8/8/2026 | 79 | 0.16 | 2 |
| 8/9/2026 | 25 | 0.05 | 2 |
| 8/10/2026 | 413 | 1.66 | 4 |
| 8/11/2026 | 104 | 2.42 | 3 |
| 8/12/2026 | 188 | 0.99 | 2 |
| 8/13/2026 | 209 | 1.73 | 3 |
| 8/14/2026 | 52 | 1.43 | 3 |
| 8/15/2026 | 6 | 0.01 | 1 |
| 8/16/2026 | 2 | 0.1 | 2 |
| 8/17/2026 | 5 | 0.01 | 1 |
| 8/18/2026 | 1 | 0 | 1 |
This payout wallet is shared: figures cover all 1,052 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.