Call the outbound API ConnectRPC, not REST

Docs-only correction, but a misleading one: chattolib speaks protobuf
over HTTP via ConnectRPC. Writing REST sent readers looking for REST
endpoints and verb semantics that do not exist anywhere in the stack.

DOCS.md

@@ -6,7 +6,7 @@ description: "Set up Hermes Agent as a Chatto bot"
 
 # Chatto Setup
 
-Hermes Agent integrates with [Chatto](https://github.com/chattocorp/chatto), a self-hosted team chat server. The adapter uses the [chattolib](https://github.com/chattocorp/chattolib) library for all API interactions, including WebSocket realtime connections for inbound message delivery and REST API calls for outbound messages. It processes messages through the Hermes Agent pipeline (including tool use, memory, and reasoning) and responds in real time. It supports text, markdown, threads, reactions, file attachments, typing indicators, and more.
+Hermes Agent integrates with [Chatto](https://github.com/chattocorp/chatto), a self-hosted team chat server. The adapter uses the [chattolib](https://github.com/chattocorp/chattolib) library for all API interactions, including WebSocket realtime connections for inbound message delivery and ConnectRPC over HTTP for outbound messages. It processes messages through the Hermes Agent pipeline (including tool use, memory, and reasoning) and responds in real time. It supports text, markdown, threads, reactions, file attachments, typing indicators, and more.
 
 The only external dependency is `chattolib[realtime]>=0.4.19`.
 
@@ -194,9 +194,9 @@ Key features:
 - **Event streaming** — all realtime events are processed through chattolib's unified event API.
 - **Auto-reconnect** — chattolib automatically reconnects with exponential backoff and resumes from the last cursor.
 
-### REST API (Outbound)
+### ConnectRPC API (Outbound)
 
-All outbound actions — sending messages, reactions, typing indicators, file uploads, etc. — use chattolib's high-level API methods, which handle authentication and error recovery automatically.
+All outbound actions — sending messages, reactions, typing indicators, file uploads, etc. — use chattolib's high-level API methods, which handle ConnectRPC calls over HTTP with authentication and error recovery automatically.
 
 ### Markdown Support
 

README.md

@@ -71,7 +71,7 @@ gateway:
 ## Features
 
 - **Realtime via chattolib** — uses the chattolib library for WebSocket realtime connections
-- **REST API via chattolib** — uses chattolib's high-level API for all outbound operations
+- **ConnectRPC via chattolib** — uses chattolib's high-level API for all outbound operations over ConnectRPC
 - **Thread support** — `GetThreadEvents` for thread replies, auto-thread creation, proper `threadRootEventId` handling
 - **DM support** — DMs always get a response, no threading in DM rooms
 - **Mention filtering** — `require_mention` (default true) with `free_response_channels` for no-tag rooms
@@ -82,7 +82,7 @@ gateway:
 
 ## How It Works
 
-The adapter uses the chattolib library to connect to Chatto, which handles both WebSocket realtime connections for inbound events and REST API calls for outbound operations.
+The adapter uses the chattolib library to connect to Chatto, which handles both WebSocket realtime connections for inbound events and ConnectRPC over HTTP for outbound operations.
 
 When a message is received, chattolib processes the event, the message is dispatched to the Hermes agent, and the response is sent back via chattolib's messaging API with proper threading.