Core Concepts
This page explains the key concepts you need to understand to use Wire effectively.
Containers
Section titled “Containers”A Container is the fundamental unit of Wire. Each container has its own MCP server, content, and access controls. Containers are queryable immediately after creation.
Container Properties
Section titled “Container Properties”| Property | Description |
|---|---|
| Name | Human-readable name (randomly assigned, can be manually changed) |
| Description | What the container is useful for (manually set) |
| Access | private (requires auth) or public (open access) |
| Paused | When paused, MCP requests are blocked |
| Sources | Entries from agent tools and file uploads |
| Tools | 5 tools: explore, search, write, delete, analyze |
Container Lifecycle
Section titled “Container Lifecycle”- Created - Container is provisioned and immediately ready
- Ready - Container accepts MCP connections and agent interactions
- Paused - MCP requests blocked (can be resumed)
- Trashed - Soft-deleted with a 14-day recovery window
- Permanently Deleted - Container and contents removed forever
Sources
Section titled “Sources”Sources are the content you add to containers. There are two ways to add content.
Agent Tools
Section titled “Agent Tools”Available on every container from creation. Agents interact with the container directly through MCP tools:
wire_explore- Discover entity types, fields, and relationshipswire_search- Query data across all modes (list, get, filter, text, semantic)wire_write- Save an entry (text, structured data, or markdown)wire_delete- Remove an entry by IDwire_analyze- Re-analyze to refresh schema and search capabilities
File Uploads
Section titled “File Uploads”Upload files through the Wire dashboard. Wire processes them into entries automatically:
- Structured files (CSV, JSON) are parsed into individual entries, one per record.
- Unstructured files (PDF, Word, text, markdown) are chunked into text entries.
Both types are available for querying through wire_search after analysis.
Supported File Formats
Section titled “Supported File Formats”- Documents: PDF, Word (.docx), Text, Markdown
- Data: JSON, CSV
- And more
See Supported File Types for the complete list.
Examples
Section titled “Examples”| Container | Content | Result |
|---|---|---|
| Wire Docs | Markdown docs, CSVs, JSON | Entity types like features, use cases, and organizations discovered with structured and semantic search |
| Lenny’s Podcast | RSS feed + transcripts | Companies and people extracted as entity types, 286 episodes searchable by topic |
Processing Pipeline
Section titled “Processing Pipeline”When you upload a file, Wire:
- Validates - Checks format and size limits
- Stores - Saves the file securely
- Parses/Chunks - Structured files are parsed into entries. Unstructured files are chunked into text entries.
Analysis runs separately. Each pass examines a portion of entries, discovering entity types and relationships. Over time, repeated passes build a complete schema available through wire_explore and wire_search.
MCP Tools
Section titled “MCP Tools”Every container ships with 5 tools. No analysis required to start using them.
| Tool | Description |
|---|---|
wire_explore | Discover entity types, fields, and relationships |
wire_search | Query data: list, get, filter, text search, semantic search |
wire_write | Save an entry to the container |
wire_delete | Remove an entry by ID |
wire_analyze | Re-analyze to refresh schema and search capabilities |
See Tools Reference for full details and parameters.
Tool Costs
Section titled “Tool Costs”Wire uses a credit system for tool calls. See the pricing page for current rates.
Organizations
Section titled “Organizations”Organizations contain users, containers, and billing information.
| Role | Capabilities |
|---|---|
| Owner | Full control, billing, delete org |
| Admin | Manage members, containers, and billing |
| Member | Full container management, read-only org settings |
See Roles & Permissions for details.
Authentication
Section titled “Authentication”Containers can be public or private (default).
- Public containers are accessible without authentication (read-only)
- Private containers require OAuth or API keys
For private containers, Wire uses OAuth 2.1:
- AI tool initiates OAuth flow
- User authorizes in browser
- Token issued with container scopes
- AI tool makes authenticated requests
See MCP Authentication for details.