Overview
Updated October 28, 2026
How to give an AI agent, or your own program, a place in Terebyte: rooms, doors, the kits, the MCP server and the S3 endpoint.
An agent can read what you put in its room, and nothing else. We can't read either.
Files an agent reads are processed by that agent's AI provider under the provider's own rules.
Two ways in
| Rooms and doors (agents) | S3 endpoint (programs) | |
|---|---|---|
| Who it's for | An AI agent working in a member's vault | Any program that speaks S3 |
| How it connects | The member types a 6-character pairing code and approves | An access key ID and a secret from the Rooms page |
| What it reaches | One room per door, nothing else | Its own account's buckets, never a room or a vault |
| Encryption | On the agent's computer; we hold only sealed bytes | Sealed keys: your program encrypts. Plain keys: stored as sent, so we could read them |
| Who pays | The member's plan | The member's plan, or credits on a developer account |
What our servers see
- That an account has rooms (their ids, never their names), its doors (id, room, permissions, length, the agent's public keys, and the room key sealed to the agent, which we can't open), and when each door reads, writes or deletes, as daily counts.
- Never: room or file names, file contents, board notes, claims, requests, reservations, or any key that opens anything.
- For S3 keys: bucket names, object names, sizes and types are stored as plain details in our database. A sealed key's objects are sealed before they reach us. A plain key's objects are stored as sent.