www.tereno.xyz
https://www.tereno.xyz/api/v1/capabilities/token.metadata/invokeShares a payout wallet with 8 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
What token is this? Read a Base token's name, symbol, decimals and total supply in one cheap typed call, with block-level freshness and explicit limitations. Identity is shared across agents for 7 days while total supply is re-read on every call beyond the block window the answer was quoted for. Positive-sum by design: $0.03 cold, $0.02 when the token identity is already shared, $0.01 on a shared full answer — and the wallet that seeded it earns a share of every reuse.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
63.3% avgResponse time
p50 126ms · p95 307msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/23/2026, 12:00:00 AM | 100% | 1 | 277ms |
| 7/24/2026, 12:00:00 AM | 100% | 1 | 111ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 185ms |
| 7/26/2026, 12:00:00 AM | 0% | 1 | — |
| 7/27/2026, 12:00:00 AM | 0% | 1 | — |
| 7/28/2026, 12:00:00 AM | 0% | 1 | — |
| 7/29/2026, 12:00:00 AM | 0% | 1 | — |
| 7/30/2026, 12:00:00 AM | 0% | 1 | — |
| 7/31/2026, 12:00:00 AM | 0% | 1 | — |
| 8/1/2026, 12:00:00 AM | 0% | 1 | — |
| 8/2/2026, 12:00:00 AM | 0% | 1 | — |
| 8/3/2026, 12:00:00 AM | 0% | 1 | — |
| 8/4/2026, 12:00:00 AM | 0% | 1 | — |
| 8/5/2026, 12:00:00 AM | 0% | 1 | — |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 258ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 87ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 90ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 288ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 110ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 220ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 127ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 205ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 48ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 167ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 145ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 47ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 65ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 102ms |
| 8/20/2026, 12:00:00 AM | 100% | 21 | 170ms |
| 8/21/2026, 12:00:00 AM | 100% | 1 | 94ms |
- Availability
- 84
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- 3
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
- GoDaddy.com, LLC
- Domain registered
- 2026-01-16
- Hosting network
- VERCEL-05
- 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 |
|---|---|---|---|
| 7/24/2026 | 48 | 0.15 | 1 |
| 7/25/2026 | 8 | 0.02 | 1 |
| 7/26/2026 | 13 | 0.03 | 2 |
| 7/27/2026 | 4 | 0.01 | 2 |
| 7/28/2026 | 46 | 0.11 | 2 |
| 7/30/2026 | 1 | 0 | 1 |
| 8/1/2026 | 2 | 0.01 | 1 |
| 8/3/2026 | 4 | 0.01 | 2 |
| 8/4/2026 | 3 | 0.01 | 1 |
| 8/6/2026 | 9 | 0.29 | 1 |
| 8/10/2026 | 2 | 0.05 | 1 |
| 8/14/2026 | 2 | 0.05 | 1 |
| 8/15/2026 | 1 | 0.02 | 1 |
| 8/16/2026 | 1 | 0.25 | 1 |
| 8/18/2026 | 12 | 0.34 | 2 |
This payout wallet is shared: figures cover all 9 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.