Skip to content

Core Concepts

This page explains the key concepts you need to understand to use Wire effectively.

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.

PropertyDescription
NameHuman-readable name (randomly assigned, can be manually changed)
DescriptionWhat the container is useful for (manually set)
Accessprivate (requires auth) or public (open access)
PausedWhen paused, MCP requests are blocked
SourcesEntries from agent tools and file uploads
Tools5 tools: explore, search, write, delete, analyze
  1. Created - Container is provisioned and immediately ready
  2. Ready - Container accepts MCP connections and agent interactions
  3. Paused - MCP requests blocked (can be resumed)
  4. Trashed - Soft-deleted with a 14-day recovery window
  5. Permanently Deleted - Container and contents removed forever

Sources are the content you add to containers. There are two ways to add content.

Available on every container from creation. Agents interact with the container directly through MCP tools:

  • wire_explore - Discover entity types, fields, and relationships
  • wire_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 ID
  • wire_analyze - Re-analyze to refresh schema and search capabilities

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.

  • Documents: PDF, Word (.docx), Text, Markdown
  • Data: JSON, CSV
  • And more

See Supported File Types for the complete list.

ContainerContentResult
Wire DocsMarkdown docs, CSVs, JSONEntity types like features, use cases, and organizations discovered with structured and semantic search
Lenny’s PodcastRSS feed + transcriptsCompanies and people extracted as entity types, 286 episodes searchable by topic

When you upload a file, Wire:

  1. Validates - Checks format and size limits
  2. Stores - Saves the file securely
  3. 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.

Every container ships with 5 tools. No analysis required to start using them.

ToolDescription
wire_exploreDiscover entity types, fields, and relationships
wire_searchQuery data: list, get, filter, text search, semantic search
wire_writeSave an entry to the container
wire_deleteRemove an entry by ID
wire_analyzeRe-analyze to refresh schema and search capabilities

See Tools Reference for full details and parameters.

Wire uses a credit system for tool calls. See the pricing page for current rates.

Organizations contain users, containers, and billing information.

RoleCapabilities
OwnerFull control, billing, delete org
AdminManage members, containers, and billing
MemberFull container management, read-only org settings

See Roles & Permissions for details.

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:

  1. AI tool initiates OAuth flow
  2. User authorizes in browser
  3. Token issued with container scopes
  4. AI tool makes authenticated requests

See MCP Authentication for details.