txt-fil.es availability and pricing

The local-first editor and public developer discovery surfaces can be evaluated without a sales conversation. The homepage supports local writing, while the public OpenAPI schema, llms.txt, MCP manifest, documentation, and non-mutating API sandbox are available without a credential. Developers can also install the official txt-cli package from npm and inspect its commands before connecting an account. These public paths let a person or agent verify the product model and response shapes without granting access to private notes.

Cloud synchronization and private workspace operations require an account and an authorized client. Signed-in users can create self-serve API keys with explicit scopes and expiration, connect through dots OAuth, and revoke access from the account dashboard. Any paid cloud entitlement, usage allowance, or checkout price shown inside the authenticated product is the authoritative offer for that account and time. txt-fil.es does not ask an agent to invent a price, submit a contact-sales form, or expose a credential merely to inspect the integration surface.

For safe evaluation, begin with GET /api/sandbox, read the developer quickstart, and use only public example data. When real files are required, the account owner should choose the smallest scopes and shortest useful lifetime, keep tokens out of URLs and note bodies, and verify the active account before syncing. Billing, account, or entitlement questions belong in the authenticated support flow so private account details are not exposed through a public page or machine-readable document.