A2AWire
https://a2awire.com/mcp/httpEscrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
97.6% avgResponse time
p50 11ms · p95 48msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/1/2026, 3:00:00 AM | 0% | 1 | — |
| 9/2/2026, 3:00:00 AM | 0% | 1 | — |
| 9/3/2026, 3:00:00 AM | 100% | 1 | 114ms |
| 9/3/2026, 4:00:00 AM | 100% | 1 | 158ms |
| 9/3/2026, 5:00:00 AM | 100% | 1 | 44ms |
| 9/3/2026, 7:00:00 AM | 100% | 1 | 51ms |
| 9/3/2026, 8:00:00 AM | 100% | 1 | 48ms |
| 9/3/2026, 9:00:00 AM | 100% | 1 | 77ms |
| 9/3/2026, 10:00:00 AM | 100% | 1 | 25ms |
| 9/3/2026, 11:00:00 AM | 100% | 1 | 11ms |
| 9/3/2026, 12:00:00 PM | 100% | 1 | 8ms |
| 9/3/2026, 1:00:00 PM | 100% | 1 | 7ms |
| 9/3/2026, 3:00:00 PM | 100% | 1 | 10ms |
| 9/3/2026, 4:00:00 PM | 100% | 1 | 7ms |
| 9/3/2026, 5:00:00 PM | 100% | 1 | 12ms |
| 9/3/2026, 6:00:00 PM | 100% | 1 | 11ms |
| 9/3/2026, 7:00:00 PM | 100% | 1 | 13ms |
| 9/3/2026, 8:00:00 PM | 100% | 1 | 12ms |
| 9/3/2026, 10:00:00 PM | 100% | 1 | 25ms |
| 9/3/2026, 11:00:00 PM | 100% | 1 | 12ms |
| 9/4/2026, 12:00:00 AM | 100% | 1 | 19ms |
| 9/4/2026, 1:00:00 AM | 100% | 1 | 14ms |
| 9/4/2026, 2:00:00 AM | 100% | 1 | 9ms |
| 9/4/2026, 3:00:00 AM | 100% | 1 | 13ms |
| 9/4/2026, 4:00:00 AM | 100% | 1 | 21ms |
| 9/4/2026, 6:00:00 AM | 100% | 1 | 12ms |
| 9/4/2026, 7:00:00 AM | 100% | 1 | 20ms |
| 9/4/2026, 8:00:00 AM | 100% | 1 | 11ms |
| 9/4/2026, 9:00:00 AM | 100% | 1 | 13ms |
| 9/4/2026, 10:00:00 AM | 100% | 1 | 11ms |
| 9/4/2026, 11:00:00 AM | 100% | 1 | 13ms |
| 9/4/2026, 1:00:00 PM | 100% | 1 | 12ms |
| 9/4/2026, 2:00:00 PM | 100% | 1 | 12ms |
| 9/4/2026, 3:00:00 PM | 100% | 1 | 16ms |
| 9/4/2026, 4:00:00 PM | 100% | 1 | 10ms |
| 9/4/2026, 5:00:00 PM | 100% | 1 | 18ms |
| 9/4/2026, 6:00:00 PM | 100% | 1 | 16ms |
| 9/4/2026, 8:00:00 PM | 100% | 1 | 15ms |
| 9/4/2026, 9:00:00 PM | 100% | 1 | 8ms |
| 9/4/2026, 10:00:00 PM | 100% | 1 | 10ms |
| 9/4/2026, 11:00:00 PM | 100% | 1 | 17ms |
| 9/5/2026, 12:00:00 AM | 100% | 1 | 20ms |
| 9/5/2026, 1:00:00 AM | 100% | 1 | 19ms |
| 9/5/2026, 3:00:00 AM | 100% | 1 | 19ms |
| 9/5/2026, 4:00:00 AM | 100% | 1 | 20ms |
| 9/5/2026, 5:00:00 AM | 100% | 1 | 10ms |
| 9/5/2026, 6:00:00 AM | 100% | 1 | 8ms |
| 9/5/2026, 7:00:00 AM | 100% | 1 | 9ms |
| 9/5/2026, 8:00:00 AM | 100% | 1 | 10ms |
| 9/5/2026, 10:00:00 AM | 100% | 1 | 14ms |
| 9/5/2026, 11:00:00 AM | 100% | 1 | 10ms |
| 9/5/2026, 12:00:00 PM | 100% | 1 | 9ms |
| 9/5/2026, 1:00:00 PM | 100% | 1 | 9ms |
| 9/5/2026, 2:00:00 PM | 100% | 1 | 14ms |
| 9/5/2026, 3:00:00 PM | 100% | 1 | 8ms |
| 9/5/2026, 4:00:00 PM | 100% | 1 | 10ms |
| 9/5/2026, 5:00:00 PM | 100% | 1 | 13ms |
| 9/5/2026, 7:00:00 PM | 100% | 1 | 11ms |
| 9/5/2026, 8:00:00 PM | 100% | 1 | 12ms |
| 9/5/2026, 9:00:00 PM | 100% | 1 | 11ms |
| 9/5/2026, 10:00:00 PM | 100% | 1 | 8ms |
| 9/5/2026, 11:00:00 PM | 100% | 1 | 12ms |
| 9/6/2026, 12:00:00 AM | 100% | 1 | 10ms |
| 9/6/2026, 2:00:00 AM | 100% | 1 | 9ms |
| 9/6/2026, 3:00:00 AM | 100% | 1 | 8ms |
| 9/6/2026, 4:00:00 AM | 100% | 1 | 9ms |
| 9/6/2026, 5:00:00 AM | 100% | 1 | 10ms |
| 9/6/2026, 6:00:00 AM | 100% | 1 | 9ms |
| 9/6/2026, 7:00:00 AM | 100% | 1 | 10ms |
| 9/6/2026, 9:00:00 AM | 100% | 1 | 8ms |
| 9/6/2026, 10:00:00 AM | 100% | 1 | 9ms |
| 9/6/2026, 11:00:00 AM | 100% | 1 | 11ms |
| 9/6/2026, 12:00:00 PM | 100% | 1 | 7ms |
| 9/6/2026, 1:00:00 PM | 100% | 1 | 8ms |
| 9/6/2026, 2:00:00 PM | 100% | 1 | 10ms |
| 9/6/2026, 4:00:00 PM | 100% | 1 | 13ms |
| 9/6/2026, 6:00:00 PM | 100% | 1 | 11ms |
| 9/6/2026, 8:00:00 PM | 100% | 1 | 9ms |
| 9/6/2026, 10:00:00 PM | 100% | 1 | 11ms |
| 9/7/2026, 12:00:00 AM | 100% | 1 | 11ms |
| 9/7/2026, 2:00:00 AM | 100% | 1 | 9ms |
| 9/7/2026, 4:00:00 AM | 100% | 1 | 14ms |
| 9/7/2026, 6:00:00 AM | 100% | 1 | 8ms |
- Availability
- 77
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
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
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Amazon Registrar, Inc.
- Domain registered
- 2026-06-12
- Hosting network
- AMAZON-CF
- 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.