api.botpay.network
https://api.botpay.network/goShares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
BotPay /go access on Base USDC
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
95.0% avgResponse time
p50 12ms · p95 451msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/11/2026, 12:00:00 AM | 100% | 1 | 367ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 77ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 9ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 8ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 13ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 12ms |
| 8/18/2026, 12:00:00 AM | 60% | 10 | 10ms |
| 8/19/2026, 12:00:00 AM | 90% | 21 | 12ms |
| 8/20/2026, 12:00:00 AM | 100% | 10 | 11ms |
- Availability
- 88
- Latency
- 100
- Security
- 94
- Transparency
- 49
- Activity
- 79
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 96% — 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
- NameCheap, Inc.
- Domain registered
- 2025-09-21
- Hosting network
- CLOUDFLARENET
- 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/20/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 7/22/2026 | 3 | 0.3 | 1 |
| 8/9/2026 | 787 | 7.87 | 723 |
| 8/10/2026 | 1,768 | 17.68 | 733 |
| 8/11/2026 | 1,366 | 119.05 | 92 |
| 8/12/2026 | 2,240 | 196.01 | 470 |
| 8/13/2026 | 2,381 | 214.07 | 565 |
| 8/14/2026 | 3,230 | 288.17 | 584 |
| 8/15/2026 | 1,843 | 161.98 | 56 |
| 8/16/2026 | 1,623 | 122.25 | 433 |
| 8/17/2026 | 1,993 | 52.6 | 546 |
| 8/18/2026 | 2,582 | 126.8 | 174 |
| 8/19/2026 | 548 | 44.9 | 21 |
| 8/20/2026 | 1,140 | 103.92 | 24 |
This payout wallet is shared: figures cover all 4 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.
Response schema
{
"properties": {
"agentIndex": {
"type": "string"
},
"message": {
"type": "string"
},
"protocol": {
"enum": [
"x402",
"mpp"
],
"type": "string"
},
"resource": {
"const": "/go",
"type": "string"
},
"testRunId": {
"type": "string"
},
"verificationCode": {
"example": "832949",
"pattern": "^\\d{6}$",
"type": "string"
}
},
"required": [
"message",
"verificationCode",
"protocol",
"resource"
],
"type": "object"
}