RAG vs fine-tuning: when to use each
RAG vs fine-tuning: RAG wins for knowledge injection and freshness, fine-tuning wins for style and format. The right choice is a context engineering call.
Your context,
everywhere.
Portable, shareable, composable context containers for AI agents.
Connect this demo container and ask your agent anything about Wire
Click to copy
https://wire-public.mcp.usewire.io/container/Kp4oRo16CXk8YBfT/mcp
Try a prompt:
How can Wire help me as a freelance consultant?
How can Wire help me stop re-uploading files to every AI?
How can Wire help my team give consistent answers?
Copy a prompt and paste it into your AI tool after connecting
Containers
Context that holds together.
Each container is an isolated environment for your context. Segment by team, project, client, or whatever makes sense. Every container gets its own database, MCP server, and API.
4,218 entries
├─ accounts.xlsx
├─ contracts.pdf
├─ agent:meeting-notes
└─ api:crm-sync
├─ contracts.pdf
├─ agent:meeting-notes
└─ api:crm-sync
932 entries
├─ features.csv
├─ teardown.pptx
├─ api:weekly-scrape
└─ agent:analysis
├─ teardown.pptx
├─ api:weekly-scrape
└─ agent:analysis
13,412 entries
├─ getting-started.md
├─ events.jsonl
└─ metrics.tsv
├─ events.jsonl
└─ metrics.tsv
Private by default
Every container is locked down with OAuth. Nothing is shared unless you want it to be.
Optionally public
Flip a container to public for read-only access when you want to share openly.
Spin up, swap, delete
Create a container in seconds. Delete it when you're done. Swap context between projects without losing anything.
Context Flow
Add anything in. Access it everywhere.
Upload files, let agents write entries, or push data through the API. Wire processes everything automatically. Connect from any MCP client or use the REST API.
Add context
Files .pdf .csv .docx .md
Agents wire_write
API REST API
├─ features.csv
├─ teardown.pptx
├─ api:weekly-scrape
└─ agent:analysis
├─ teardown.pptx
├─ api:weekly-scrape
└─ agent:analysis
Access anywhere
https://wire-public.mcp.usewire.io/container/Kp4oRo16CXk8YBfT/mcp
Works with 
+ any MCP client
+ any MCP client Any file type
PDF, Word, CSV, JSON, markdown, and more. Upload through the dashboard or the REST API.
Agent writes
Agents write entries directly via MCP. Notes, structured data, and markdown, all tracked by source.
MCP + REST API
One URL per container for any MCP client. Full REST API for automations and pipelines.
competitor-intel 932 entries
Intelligence
A knowledge graph, not a file dump.
Wire analyzes your content, discovers entities and relationships, and maps the connections between them. People, companies, features, decisions. Structured for retrieval, not just storage.
Collaboration
Shared context, shared understanding.
Multiple users and agents access the same container simultaneously. Role-based access, shared credit pool, real-time updates. Everyone works from the same context, always in sync.
Frequently asked questions
Everything you need to know about Wire.
Still have questions? Get in touchWhat is Wire?
Wire creates and manages composable context containers. Add your documents, structured data, or let your agents write entries directly. Wire automatically organizes everything for AI consumption. Your agents access context through MCP. Portable intelligence that works across all your AI tools.
How does it work?
Create a container for your project, team, or use case. Add context through file uploads or let your agents write entries directly. Wire automatically organizes and structures everything into AI-optimized context. Connect from Claude, Cursor, or any MCP-compatible tool.
What file types do you support?
Wire supports common document formats including PDF, Word documents, text files, markdown, CSV, JSON, and more. See the full list of supported file types.
What AI tools work with Wire?
Wire works with any AI tool that supports MCP (Model Context Protocol). This includes Claude Desktop, Claude Code, Cursor, Cline, and more. See setup guides for all supported tools.
What is a composable container?
Each container is private by default and holds your documents and structured data. Wire automatically organizes and structures everything based on what's inside, making your data accessible to agents without manual configuration. Containers adapt to their content.
Can I share containers with my team?
Yes! Wire is built for teams. Invite team members to your organization and everyone can access shared containers. Each team member connects their own AI tools to the same context, so everyone stays on the same page.
Is my data private?
Yes. All containers are private by default and only accessible to you and the team members you explicitly invite. We never share your data with third parties or use it to train AI models.
How does pricing work?
Every new organization gets 3,000 starter credits to try Wire. Pick a plan for monthly credits and the option to buy additional credit packs. All plans include unlimited containers, team members, and MCP access. See our pricing page for details.
From the blog
Context engineering, AI agents, and what we're learning.
Context budgets: how to allocate tokens for AI agents
A practical guide to context budgets for AI agents. How to allocate tokens across system prompts, tools, retrieval, history, and a buffer in production.
Context Poisoning: When Bad Data Becomes AI Ground Truth
Context poisoning plants false data into an AI agent's memory or RAG index. The model treats it as truth. It's a context engineering problem, not a model bug.
Try wire-memory Persistent memory for Claude Code and Cursor, powered by Wire containers.