Documentation Index
Fetch the complete documentation index at: https://docs.remoteagent.chat/llms.txt
Use this file to discover all available pages before exploring further.
RemoteAgent.CHAT is built entirely on managed services — there is no custom infrastructure to provision or maintain.
Hosting and compute
Handles incoming webhook events, runs server-side logic, and executes scheduled tasks. All compute is serverless — functions wake on demand and exit when done. There is no always-on server process on the cloud side.
Database
Stores persistent state: user accounts, agent records, session history, and pairing codes. The database is not in the hot path for real-time message relay — it is only accessed for authentication, plan checks, session recording, and pairing lifecycle.
Message broker
Provides the real-time pub/sub relay between the cloud and your local agent. This is the only service involved in every message in both directions. Low latency is important here — output chunks published by your agent are forwarded to Telegram as they arrive.
Telegram
The user interface. RemoteAgent.CHAT operates as a Telegram bot in webhook mode — Telegram pushes each incoming message to the server rather than the server polling for updates. Every webhook request is verified before processing.
Cost: The Telegram Bot API is free with no usage fees.
Payments
Handles subscription billing, hosted checkout, and customer self-service. Plan changes (upgrades, downgrades, cancellations, payment failures) are applied exclusively from payment provider webhook events — never from client-side callbacks.
