Your agent on Telegram. Free.
Pick a template, give it a name and a personality, paste a bot token from BotFather, and it is live in under a minute. It runs on our relay day and night, with our model. No key, no account, nothing to buy.
Checking the relay…
- No API key
- No signup
- Reads Robinhood Chain prices
- Price alerts and a daily digest
- Searches the web, names its sources
- Runs while you sleep
Deploy in four steps.
The only thing you fetch is a bot token from Telegram. Everything else is a name and a few sentences.
Your agents.
Deployed from this browser. The owner token that controls them is kept here, in local storage, and nowhere else.
None yet.
Keep them across devices
Optional. Sign in with an email through Privy and attach your agents to that account; on another phone or browser, sign in again and recover them. The relay keeps a salted hash of the account id, never the email.
What is real.
The same table every HEXCOMB page has: what happens to what you give us, with nothing left out.
| Where the bot token goes | To our relay, encrypted at rest under a key on that server, decrypted to call Telegram. So the relay can read the token at run time; a service that could not would not be able to answer as your bot. It is never shown back and never logged. |
|---|---|
| What we keep | The agent's name, template and brief, and message counts. Alert levels and digest times are kept per chat id, because they have to fire while nobody is talking. The last twelve turns of each chat are kept in memory for context, never written to disk, and gone when the relay restarts. We do not read your chats. |
| Whose model | Ours, paid by us. The status line above says when it is connected. Until then every agent still runs and answers prices on Robinhood Chain; for anything else it says its model is being connected. |
| Limits | Three agents per browser, ten per address per day and twenty deploy attempts per address per day, sixty messages per chat per day, six hundred per agent per day, one message per chat every one and a half seconds. The whole service has a daily ceiling on model calls; past it, every agent answers prices only and says the model rests until midnight. In a group the agent answers when mentioned, replied to, or given a command. Limits reset at midnight UTC and may change; the page states the current ones. The relay keeps a salted hash of your address for the daily counts, never the address. |
| Across devices | Optional. Sign in with an email through Privy and your agents can be attached to that account and recovered on another device. The relay asks Privy to confirm the sign-in and keeps a salted hash of the account id; your email stays with Privy. Without sign-in, the owner token in this browser is the only key to your agents. |
| The web | The agent can search the web and read public pages through the same keyless public reader the comb uses, at most once per message and twenty times per chat per day. A page named in a question is read first. Answers say which page they came from. Private and internal addresses are refused. |
| What it is not | No trading, no wallet, no signing, no token. A free agent that talks. If it should do more, open the comb with your own key. |
Want your own keys and cells?
The comb runs agents in your browser with your own API key: chat, code, browser, tasks and the chain.