semagram.io: Semantic search API for Telegram. Search across 1M channels, 150K chats, and 100K bots using hybrid search (embedding similarity + BM25 keyword matches).
https://semagram.io/api/agent/searchSemantic search API for Telegram. Search across 1M channels, 150K chats, and 100K bots using hybrid search (embedding similarity + BM25 keyword matches).
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
79.0% avgResponse time
p50 501ms · p95 549msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/7/2026, 12:00:00 AM | 100% | 15 | 492ms |
| 9/8/2026, 12:00:00 AM | 100% | 20 | 499ms |
| 9/9/2026, 12:00:00 AM | 100% | 21 | 495ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 492ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 490ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 496ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 500ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 507ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 506ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 502ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 524ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 501ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 501ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 514ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 496ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 512ms |
| 9/23/2026, 12:00:00 AM | 100% | 12 | 516ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 497ms |
| 9/25/2026, 12:00:00 AM | 100% | 14 | 490ms |
| 9/26/2026, 12:00:00 AM | 100% | 13 | 508ms |
| 9/27/2026, 12:00:00 AM | 100% | 14 | 495ms |
| 9/28/2026, 12:00:00 AM | 100% | 12 | 499ms |
| 9/29/2026, 12:00:00 AM | 92% | 12 | 521ms |
| 9/30/2026, 12:00:00 AM | 0% | 10 | — |
| 10/1/2026, 12:00:00 AM | 0% | 1 | — |
| 10/2/2026, 12:00:00 AM | 0% | 1 | — |
| 10/3/2026, 12:00:00 AM | 0% | 1 | — |
| 10/4/2026, 12:00:00 AM | 0% | 1 | — |
| 10/5/2026, 12:00:00 AM | 0% | 1 | — |
- Availability
- 95
- Latency
- 92
- Security
- 100
- 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
- BTC
- Networks
- lightning
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- 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.
Response schema
{
"items": {
"properties": {
"avatar_url": {
"type": "string"
},
"bio": {
"type": "string"
},
"description": {
"type": "string"
},
"id": {
"description": "Stable identifier of the entity",
"type": "integer"
},
"kind": {
"type": "string"
},
"name": {
"type": "string"
},
"user_count": {
"type": "integer"
},
"username": {
"type": "string"
}
},
"required": [
"id",
"username"
],
"type": "object"
},
"type": "array"
}