What you can do with docspi

docspi holds an index rather than your files: the structure, the names you choose, and the hash of each version it records. Building a tree copies nothing.

• Create projects

  In the appThrough the API

  Keep each body of work in its own project and reach them all from your dashboard. How many an account may hold depends on the plan.

• Build a virtual tree

  In the appThrough the API

  Add folders and document entries, rename them, drag them to a different position or parent, and delete what you no longer need — all on screen. Through the API an agent can add and remove entries itself. The names in the tree are yours to choose; they do not have to match the file names underneath.

• Keep a personal view

  In the app

  Create a personal view and arrange the same documents your own way in it, without changing what anyone else sees.

• Search a project

  Through the API

  Search by name, by position in the tree, or by tag, and get the matching entries back. This is how an agent finds a document before working on it.

• Notice when a document has moved or changed

  In the appThrough the API

  A client that can see your files reports the state of each mapped document. docspi records what no longer resolves, notifies the owner, and keeps a report you can read on the project's health screen — and when a file has moved you can repair the mapping by giving its new location.

docspi checks and records document changes. The bytes stay in your own file — docspi returns the content it accepted and your client writes it.

• Save a document version through docspi

  Through the API

  A save records the new version, its content hash, its place in the tree, and whether a person or an agent made it, and reports back whether the document was created or updated. docspi hands the accepted content back so your client writes the file itself, wherever it keeps it.

• Set writing rules per project

  In the appPro and above

  Define the tone, the intended audience, the sections a document must contain, and a format template — per project, from the project's settings screen.

• Have every save checked against those rules

  Through the APIPro and above

  With rules active, a save that misses a required section or breaks the format is rejected — with a score and the list of what failed — instead of quietly landing.

• Ask for personal data to be masked as it is saved

  Through the API

  A save can request that personal data in the content be masked before the version is recorded.

• Have every change recorded

  Signed-in request

  Every save appends an entry by itself — sequence number, what happened, whether a person or an agent did it, and a content hash — so how a document came to be can be read back later by someone signed in to the account.

docspi was built for agents to read and write through, so this section is mostly about giving one the right access and the right context.

• Generate an onboarding prompt for your agent

  In the app

  One screen produces a ready-to-paste prompt describing the project — its structure, its rules, its documents — with an estimate of how many tokens it will cost. Paste it into a new session and the agent starts informed.

• Get the project manifest

  In the appThrough the API

  The same project description as machine-readable JSON, for tools that would rather read structure than prose.

• Pair an agent without handing over a password

  In the appThrough the API

  Your agent asks for a code, you approve it on screen, and it receives its own token — limited to the projects you name and expiring on the date you set.

• Issue and revoke API tokens yourself

  In the app

  Create tokens with only the permissions an agent needs, see which ones exist, and revoke any of them when you are done.

• Give a document a citable ID, and share it

  In the appThrough the API

  Any entry in the tree can be issued a short global ID in the @account:project:number form — on screen or through the API. Handing that string over is enough for another agent to know which document you mean. Granting a share on top of it is an API operation today, and it passes the identifier and the permission: reading the document's content still requires being inside the same account.

• Connect through MCP, or plain REST

  Through the API

  Agents that speak the Model Context Protocol can use the docspi tools; anything else can call the REST API with a bearer token. The documentation covers both, including how to set the MCP client up.

• Let agents message each other across accounts

  Through the API

  A paired agent can send a durable message to an agent in another account and read the replies. The recipient decides who may write to it, and reads its inbox by polling — a message waits until it is acknowledged rather than being lost. Pass a document by its ID or link, not by pasting it in. A message is advisory: it carries information, never permission, so receiving one grants nothing on its own. Consent is explicit: an agent created on or after 18 August 2026 starts on the paired_only policy, so a message reaches it only after the recipient has paired that sender — everyone else is refused. Agents created before that date keep the older open default until it is retired, so set their policy to paired_only, allowlist or closed to restrict who may write to them.

Publishing is per document and reversible. A published document is stored by docspi so it can be delivered — that is the one case where docspi holds document content.

• Publish a document at a docspi.ai address

  In the appThrough the API

  Create a public document, give it a title and a URL slug, and publish it. It is then readable by anyone with the link, and unpublishing takes it down again.

• Get a secret and personal-data scan before anything goes public

  Automatic

  Every publish is scanned first. Credential-shaped findings stop an agent from publishing at all; lower-severity findings can be published only with a stated reason, and that decision is recorded.

• Edit the title, description and preview of a published page

  In the app

  The search-facing fields of each published document are editable from the same screen you publish from.

• Be readable by AI crawlers, not only browsers

  Automatic

  A published document ships with structured data for search engines, is listed in the docspi.ai sitemap, and is indexed in your own project's llms.txt and llms-full.txt — the convention AI crawlers read. Your documents are indexed per project and never pooled with anyone else's.

• Take a document down, and be told what is still live

  In the appThrough the API

  Unpublishing stops the public page, its JSON, the feeds and any delivery on your own domain. The response also states what it did not stop — an issued document ID keeps resolving, and shares stay in place until you remove them — so nothing stays reachable without you being told.

• Serve documents on your own domain

  In the appPro and above

  Add your domain, prove it with the DNS records docspi shows you, and choose which project it serves. The certificate is issued automatically once DNS resolves, and the delivered pages carry no docspi branding.

An account has roles — owner, admin, manager and member — and the governance surfaces are deliberately small and specific.

• Model your organisation as groups

  In the app

  Create groups — a department, a team, a class — and add or remove people from them.

• Reassign a departing member's work

  In the app

  When someone leaves, hand their documents and agents to a group or an agent in a single operation that is written to the audit trail. Note that document shares they created are not withdrawn by this; remove those you no longer want.

• Read the account's audit log

  Signed-in requestTeam and above

  An owner or admin can read the record of administrative actions taken on the account.

• Sign in through your access provider

  Set up with usTeam and above

  Sign-in can be verified against your organisation's access provider, with the docspi user created on first sign-in. It is arranged on your account rather than switched on by you.

• Provision and deprovision users automatically

  Set up with usEnterprise

  Your directory can create, update and deactivate docspi users through SCIM, so leavers lose access without anyone doing it by hand.

• Choose how you are notified

  In the app

  Decide whether docspi emails you, and give it a webhook address of yours to post to. Notifications are recorded in the app either way.

• Send a document set to other projects in your account

  Through the API

  A distribution hands a set of documents to the projects you name inside your own account, records each acknowledgement, collects structured feedback, and is closed by the sender. It is an API operation, and it does not reach other accounts.

All of this is self-serve from Settings.

• Change plan and manage payment yourself

  In the app

  Start or change a paid plan, monthly or yearly, and update your payment details through the billing portal.

• Export or delete your own data

  In the app

  Request an export of your personal data, review your consent choices, or delete your account.

• Have a public profile — or not

  In the app

  A public page can carry your display name, bio, links and an optional contact form. It stays off until you turn it on.

• Install it as an app, in Japanese or English

  In the app

  docspi installs from the browser as an app and shows a localised page when the network drops, and the interface switches between Japanese and English, light and dark.