Questions, answered
Frequently asked,
clearly answered.
How Relay handles your Aicoo key, what an agent can and cannot see, when a human gets pulled in, and where your data lives.
- How is my Aicoo key stored?
- Server side, and only server side. When you connect, Relay validates the key against Aicoo and writes it to storage that the browser never reads. Your identity in the app is an httpOnly cookie, so the key itself is not in the page, not in the JavaScript bundle, and not in any log line. Requests to a teammate are signed with their key on the server, never yours, and never in the response.
- What can another person's agent see?
- Only the context that person allowed it to see. Each agent answers from its owner's permitted Aicoo context, nothing wider. When you relay a question, you are reaching one person's agent and the material they chose to make answerable. There is no shared corpus that pools everyone's documents together.
- When does it escalate to a human?
- When the topic is genuinely new or sensitive. If the agent cannot answer with confidence from permitted context, it stops rather than guesses. Relay marks the request escalated and notifies the human through Aicoo's send_message_to_human, with the full thread attached so they have the question and everything the agent already tried. The person becomes the exception, not the default.
- Where is my data stored?
- In Upstash Redis. Member records, relay requests, and message threads live there. It was chosen for fast reads and one-click provisioning on Vercel. Your Aicoo key is part of the member record on the server and is never returned to a client.
- Do you support Google or GitHub login?
- Today your identity is your Aicoo connection. You connect your agent once and a session cookie keeps you signed in. Broader OAuth, including Google and GitHub, arrives when Aicoo releases its own OAuth. Until then Relay uses the sanctioned API-key model, where each person's own key acts on their behalf.
- What does it cost?
- Relay starts free for small teams and scales by seat. See the pricing page for the three tiers. Figures shown there are illustrative and subject to change.
- How is this different from a shared Q&A bot?
- A shared bot answers from one knowledge base. Relay routes to a specific person's permitted context. The unit is a person, not a corpus. You ask the colleague who owns the answer, their agent responds, and only that person is pulled in if the agent cannot help. It is person-to-person agent routing, not one big assistant standing in for the whole company.