Limits
Wire has the following limits for containers and files.
All paths include unlimited containers, unlimited team members, and full MCP access. They differ in how you pay and whether you get a monthly credit allotment.
| Path | Price | Monthly Credits | Credit Pack Bonus |
|---|---|---|---|
| Pay as you go | $0 | 1,000 starter grant on signup, then credit packs | None |
| Wire Pro | From $20/mo | 20,000–500,000/mo (pick the amount that fits) | +10% bonus on every pack |
| Enterprise | Custom | Custom | Contact sales |
Wire Pro amounts
Section titled “Wire Pro amounts”One subscription, five amounts. Switch between them anytime. Upgrades prorate immediately, downgrades take effect at the end of the current cycle.
| Amount | Monthly Credits | Monthly Price |
|---|---|---|
| 20k credits/mo | 20,000 | $20/mo |
| 50k credits/mo | 50,000 | $50/mo |
| 100k credits/mo | 100,000 | $100/mo |
| 200k credits/mo | 200,000 | $200/mo |
| 500k credits/mo | 500,000 | $500/mo |
Credit Expiration
Section titled “Credit Expiration”- Monthly subscription credits expire 7 days after the billing cycle ends (no rollover).
- Purchased credit packs are valid for 12 months from purchase.
- Starter grant credits are valid for 12 months.
- Credits are consumed in FIFO order, soonest-expiring credits are used first.
Credit Costs
Section titled “Credit Costs”| Action | Cost |
|---|---|
| Container storage | 1 credit per 1,000 entries per day, capped at 100 credits/day per container |
wire_explore, wire_navigate | 1 credit per call |
wire_search (hybrid retrieval) | 5 credits per call |
File download (MCP resources/read) | 2 credits per fetch |
| Provenance graph | 1 credit per entry written, when the container has it on |
| Entity graph | 1 credit per entry written, when the container has it on |
wire_write, wire_delete, file uploads, container creation, contextual enrichment | Free |
Storage is metered once per day at midnight UTC. Empty containers (zero entries) charge nothing. The 100 cr/day cap is a pricing ceiling. Containers can grow past that without the daily charge increasing further.
The two analysis graphs
Section titled “The two analysis graphs”Wire builds two optional graphs over what you save, and each is a switch on the container’s settings page. Both are on by default.
- The provenance graph records how a new entry relates to what the container already held: whether it corroborates, elaborates on, supersedes or contradicts its nearest neighbours.
- The entity graph records what your context is about — the people, companies, projects and other things that recur across entries, and how they connect.
Each charges 1 credit per entry written, and only when it actually runs. A file that lands as 200 entries with both graphs on costs 400 credits to analyse; with the entity graph switched off it costs 200; with both off it costs nothing beyond storage. The write itself is always free, and each entry is billed once per graph — a retried or re-driven analysis never bills twice.
Contextual enrichment, which is what makes a search hit come back with the surrounding context rather than a bare fragment, is not one of the two. It runs on everything you save, has no switch, and is free.
If the organization’s balance is below the grace floor, the write still succeeds and the analysis is skipped rather than queued. The skip is recorded in the container’s activity feed, and analysis resumes on new writes once the balance is topped up.
File Limits
Section titled “File Limits”| Limit | Value |
|---|---|
| Maximum file size | 50 MB |
| Maximum indexed file size (PDF) | 50 MB |
| Maximum indexed file size (other types) | 25 MB |
| Maximum upload over the REST API | 25 MB |
| Maximum upload as an MCP tool argument | 1 MB |
PDFs are converted and indexed up to the full 50 MB cap, including scanned documents, which are transcribed with OCR. Other file types between 25 MB and 50 MB are stored and available for download, but are not indexed for search.
The 50 MB cap is what a container will store; the two upload caps are what each entry point will carry. Anything above 25 MB uploads from the dashboard.
Container Limits
Section titled “Container Limits”| Limit | Value |
|---|---|
| Maximum entries per container | 100,000 |
A container at the entry limit keeps serving reads and deletes. New writes are declined until entries are removed. Higher limits are available on enterprise plans.
Write Limits
Section titled “Write Limits”| Limit | Value |
|---|---|
Maximum size per wire_write call | 32,000 tokens (roughly 128 KB of text) |
Writes over 8,000 tokens are automatically split into linked chunk entries. Content larger than the per-call cap should be uploaded as a file instead, where the file pipeline chunks and indexes it without this limit.
Ephemeral Container Limits
Section titled “Ephemeral Container Limits”Ephemeral containers are created via instant onboarding without an account.
| Limit | Value |
|---|---|
| Container lifetime | 7 days |
| Starter credits | 1,000 |
| Containers per anonymous session | 1 |
Ephemeral containers receive the same 1,000 starter credits as any new organization. Once those credits are spent, the paywall applies until the container is claimed and moved to an organization with a funded balance. The two surfaces report it differently: REST API and embed calls return HTTP 402 with an INSUFFICIENT_CREDITS error, while over MCP the call itself succeeds at the protocol level and the tool returns an error result saying there are not enough credits to run it. Contextual enrichment is free and continues to run; it’s the read tools, the two analysis graphs, and daily storage charges that draw down the balance.
After 7 days, unclaimed ephemeral containers and their associated anonymous accounts are automatically deleted. Claim your container before then to keep it permanently.