developers
Build on connected text
txt exposes one synchronized text filesystem through REST, a zero-dependency TypeScript SDK, txt-cli, and a remote Model Context Protocol server. Integrations can list metadata without downloading file bodies, read content with ETags, write conditionally with If-Match, replay mutations safely with idempotency keys, and consume an ordered change feed. Files, folders, versions, tags, context, connections, comments, shares, skills, devices, and transcriptions use the same account model across clients.
Begin without credentials by reading the discovery documents, OpenAPI schema, llms.txt, and sandbox. When private data is required, the account owner creates a self-serve key with only the necessary scopes and an explicit expiry, or authorizes a first-party client through dots OAuth. Production responses include request IDs, standard rate-limit fields, and structured errors with resolution guidance so an agent can recover without scraping an HTML page.
Authentication
Create scoped, expiring API keys or connect through dots OAuth and RFC 9728 discovery.
REST API
Explore the versioned API, execute requests, and download the OpenAPI 3.1 contract.
MCP
Connect an MCP client to the Streamable HTTP endpoint and inspect the public server manifest.
Sandbox
Read or post example requests against a zero-auth, non-mutating response simulator.
Versioning
Understand stable v1 paths, compatibility, deprecation, and Sunset signaling.
Agent instructions
Learn when agents should use txt and the safe sequence for workspace operations.