Bay Run
https://bay-run-mvp-zfmlsu2yla-uc.a.run.app/mcpDiscover, prove & serve small open specialist models: embeddings, rerank, extract — OpenAI-compat.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
83.3% avgResponse time
p50 258ms · p95 464msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 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 | 100% | 1 | 106ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 120ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 106ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 101ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 272ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 311ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 289ms |
| 8/18/2026, 12:00:00 AM | 100% | 5 | 300ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 301ms |
| 8/20/2026, 12:00:00 AM | 100% | 15 | 263ms |
- Availability
- 96
- Latency
- 100
- Security
- 99
- Transparency
- 61
- 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
- MarkMonitor Inc.
- Domain registered
- 2018-04-05
- 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.
Response schema
{}