LoginSign Up
← Back to all sparks
D

Document360

COLLAB
Velocity6.3

Document360 rebuilds its public API and turns docs into an agent-readable surface.

apioauthmcpknowledge baseenterprise accessai discoverability
◆Current state
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
◆Where it's heading
The product is being rebuilt around programmatic access rather than portal usage. MCP made the knowledge base writable by an assistant, llms.txt made it discoverable to crawlers, copy-as-Markdown and open-in-ChatGPT made articles portable, and API v3 now gives all of that a permission-aware substrate the old v1/v2 endpoints could not support. The same permission model is showing up on the reader side too — Eddy AI features are now gated per reader group — so authorization is becoming the shared spine across API, AI, and reader access.
◆Prediction
Expect the advanced API v3 endpoints to keep expanding as a paid add-on and the MCP server to be re-plumbed onto v3's scoped-key model, since MCP currently sits outside the new authorization scheme. A v1/v2 deprecation notice is the other likely follow-up.

◆Recent moves

  1. 1d ago

    API v3 rebuild adds OAuth 2.0 and scoped API keys

    ⚡ SPARK

    API v3 is a ground-up rebuild of the public REST API with OAuth 2.0, scoped API keys, and coverage extending to users, roles, reader access, drive, and analytics. It gives the automation and AI work of the last six months an authorization model the older endpoints never had.

    View source ↗
  2. 8d ago

    Interactive API reference with a rebuilt Try It! console

    The API reference gets a three-pane layout, a rebuilt Try It! console with live schema validation, in-console authorization, reusable session variables, and inline Eddy AI answers. It targets the reader side of the same API-first push that API v3 serves on the writer side, and Widget 2.0 begins rolling out alongside it.

    View source ↗
  3. 29d ago

    Find and replace spans variables, snippets, and links

    Global find and replace now reaches variables, snippets, glossaries, and hyperlink URLs in one operation, PDF exports gain section re-ordering, and readers can copy articles as Markdown or open them in ChatGPT or Claude. The reader-side additions continue the pattern of treating documentation as input for someone else's assistant.

    View source ↗
  4. 1mo ago

    Native Mermaid diagrams and automatic llms.txt generation

    Mermaid diagrams become native to the WYSIWYG editor with 23 templates and a live-preview split pane, and llms.txt is now generated automatically for agent discoverability. Both reduce the number of external tools sitting between a doc and the systems that read it.

    View source ↗
  5. 1mo ago

    MCP server gains publishing and workflow controls

    The MCP server extends from read-and-write into lifecycle control: listing workflow statuses, assigning reviewers, moving articles between stages, and publishing or unpublishing. It closes the gap that forced an assistant-driven edit to finish manually in the portal.

    View source ↗
  6. 2mo ago

    Multiple JWT configs and an MCP analytics dashboard

    Up to five JWT configurations per project, a dedicated MCP analytics dashboard, and reader permission inheritance for categories. The JWT and inheritance work is enterprise access plumbing; the MCP dashboard is the first sign the company is measuring assistant traffic as its own channel.

    View source ↗