FAQ

No, and you are not meant to. Your agent captures as the work happens. If you find yourself maintaining Contextaco by hand, something has gone wrong — the whole point is that you do not keep a second system.

There is one interface: MCP. No SDK, no library, nothing to install. That is deliberate — the consumer of this is an agent, and agents already speak MCP.

It makes no model calls of its own. It stores and serves; your agent does the reasoning.

Markdown, under handles, referencing each other by handle. There is nothing to export because there is nothing proprietary to export from — what you read is what is stored.

Yes, by default. Publishing is an explicit act, never a side effect.

Anyone, with no account needed — including forking it. That is the point of publishing; treat it as irreversible in practice, because a fork someone else made stays theirs.

A fork copies what the person forking can already read. Publishing decides what is readable.

Yes. Your writing keeps whatever history a checkpoint already recorded, so removing it takes it out of the current state without erasing the past — that is what makes the record trustworthy. Writing that was never checkpointed has no history to keep and goes entirely. Files are different: they have no history, so removing one always takes it and its bytes for good.

Yes, always. A file’s bytes never change, so there is no version of it for a checkpoint to hold on to — deleting one gives the space back whether or not it had been part of your work for months. The same is true when you remove the entity a file is attached to: the file goes with it and the bytes come back.

Because someone changed that content after your agent read it. You get the current content and a diff back, so the change can be redone on top rather than silently overwriting. See Troubleshooting.

Because forbidden would confirm it exists. Not found is the honest answer to someone who is not entitled to know either way.

It is the first half of every address you have published, and it is chosen once. An agent that could set it could permanently settle something only you should settle. Display name and bio are changeable and an agent can update them.

Forking exists because an intention diverged. Merging would collapse two lines of work that diverged for a reason, and quietly pick a winner. Reading across a family and reporting where they disagree is a different operation, and a better one.

Reading a taco returns its shape — metadata, the description, and a map of entities — not every body. An agent’s context window is the scarce resource, so bodies are fetched only when needed.

Free to start, with a storage ceiling. Paid tiers raise it, and raise the size of a single file you can attach. Those are the only two things a paid tier changes.

Pricing states the figures

Writes stop; reads never do. Nothing you published becomes unreadable, and nobody loses access to work you shared.

As many as you like, public or private, on every plan — along with unlimited agents and tokens. Making one is never the thing you pay for, because capturing your work is the point of the product.

There is a ceiling, far above any ordinary use, that exists only to stop a runaway agent exhausting your account in a loop. You will not meet it by working.

Say it to your agent, in the moment, in whatever words you would use: that a name misled you, that you could not find something, that a refusal made no sense, or that you wish it did something it does not. Your agent can pass that straight through to us, in your words, without you leaving what you were doing.

Nobody replies there, so it is not the route for a question you need answered — it is how the thing that annoyed you reaches the people who can change it. If you would rather write to a person, or you want an answer, email hello@contextaco.com.