Public Containers
By default, Wire containers are private. Only authenticated members of your organization can access them. Making a container public lets anyone with the URL query its contents without signing in.
When to Use Public Containers
Section titled “When to Use Public Containers”Public containers are useful when you want to share context openly:
- Publish documentation or knowledge bases that AI agents can query
- Let external collaborators access data without creating Wire accounts
- List your container in the Wire Explore directory for discovery
Making a Container Public
Section titled “Making a Container Public”- Open your container in the Wire dashboard
- Go to Container Settings
- Toggle Public Access on
Only Owners and Admins can change container visibility. See Roles & Permissions for details.
What’s Accessible Without Authentication
Section titled “What’s Accessible Without Authentication”Public access is read-only. Here’s what unauthenticated visitors can and cannot do:
| Tool | Public Access |
|---|---|
wire_explore | Yes |
wire_search | Yes |
wire_write | No |
wire_delete | No |
wire_analyze | No |
wire_claim | No |
Write tools are hidden from public MCP clients entirely. They don’t appear in tools/list.
REST API
Section titled “REST API”| Endpoint | Public Access |
|---|---|
GET /container/:id/status | Yes |
GET /container/:id/files | No |
POST /container/:id/files | No |
DELETE /container/:id/files/:fileId | No |
POST /container/:id/claim | No |
See the REST API reference for full endpoint documentation.
Authenticated Users
Section titled “Authenticated Users”Users who connect with an API key or OAuth token have full access to all tools and endpoints, regardless of whether the container is public or private.
Credit Usage
Section titled “Credit Usage”Public visitors still consume credits from your organization’s balance. Each wire_explore and wire_search call costs credits just like authenticated usage. Monitor your usage in the dashboard billing section.
Making a Container Private Again
Section titled “Making a Container Private Again”Toggle Public Access off in Container Settings. Access is revoked immediately. Unauthenticated requests will start returning 401 Unauthorized.
Next Steps
Section titled “Next Steps”- Authentication — OAuth and API key setup
- REST API — Programmatic container access
- Roles & Permissions — Who can change visibility