New governed REST endpoints, MCP tools, and resources cover courses, curriculum, enrollment, multimodal content mapping, AI Tutor, study artifacts, persistent quizzes, progress, and human guidance.
Developer platform updates
What changed in DocIntel
Follow available capabilities, contract updates, new scopes, security controls, and integration guidance without guessing from product behavior.
September 2026
Learning, usage governance, credential hardening, and public contracts
REST and MCP activity now records application, workspace, scope, operation, outcome, latency, bytes, tokens, request IDs, and trace IDs.
Apply atomic limits by organization, application, workspace, scope, operation, or combined dimensions.
Use multiple active secrets during bounded rotation overlap, independent expiry, last-used visibility, and explicit revocation.
Optionally restrict Client Credentials token issuance to approved IPv4 or IPv6 networks.
Export a public-only REST contract without internal developer administration routes.
Begin with dependency-light Python, JavaScript, and Java clients; packaged registries remain planned.
August 2026
Enterprise integrations became durable and observable
Organization-owned service clients gained approved scopes, explicit team workspaces, and Client Credentials access.
Versioned contracts cover workspaces, content, knowledge, large uploads, batches, operations, events, reviews, and artifacts.
OAuth-secured tools and resources cover content, knowledge, sessions, video, workflows, review, packets, and batch operations.
Applications can manage HTTPS subscriptions, event filters, delivery attempts, retries, replay, and signing-secret rotation.
Trace Explorer connects user requests with retrieval, reranking, prompts, tools, models, operations, evaluations, SLOs, and alerts.
Direct cloud upload, jobs, checkpoints, leases, retries, heartbeats, parallel stages, dead-letter recovery, and resumable processing support large media.
Release discipline
How to interpret status
| Status | Meaning |
|---|---|
| Available | Implemented and documented for current deployments. |
| Starter | Working source intended to accelerate integration but not yet distributed through a package registry. |
| Beta | Usable with expected contract or operational refinement. |
| Planned | Directional capability that should not be treated as a current production contract. |
Check the contract before release
Pin and compare OpenAPI schemas, request newly introduced scopes explicitly, and test against a non-production team workspace before upgrading an enterprise integration.
Next packaging increment
Planned developer experience
Versioned PyPI packageVersioned npm packageVersioned Maven artifactGenerated model coverage beyond starter methodsAutomated compatibility reportsExpanded conformance fixtures