sieve bronze
telemetry.overlay365.online
“Local, no-GPU code-context layer: index, retrieve, pack, verify, guard.
https://telemetry.overlay365.online/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 21 Jan 2027 as of our check on 11 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE1 under ISRG Root X2 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
telemetry.overlay365.online. - Connection
- TLS 1.3 Β· X25519 β classical key exchange, agreed with our checker on 11 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 11 Nov 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS14618)
- Last checked
- 3d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of telemetry.overlay365.online controls every word below.
Pack context
Retrieve and pack repo context under a token budget.
Verify
Stale-memory, hallucination, and injection/secret checks.
What kind of listing
- Private endpoint: Its card names an endpoint on 0.0.0.0, which is not reachable from the public internet.
Checked by agenttru.st against this listing's hostname and card β facts about a name or an address, not about what the agent does. How kinds are decided.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Overlay365 β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.2.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing β they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://telemetry.overlay365.online/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.