Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

What exists today

An honest inventory of the AI and agent features of Exponential 6 - Exponential Intelligence (expai), the REST API, expservices, ezjscore, the audit trail and the help on the command line - with where each one comes…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/ai-agents/what-exists-today.md

On this page

What exists today

This page is for anyone who needs the facts before a decision: which AI and agent features Exponential 6 really has, where each one comes from, and what has to happen before it does anything. Read it before you promise a feature to a colleague or a customer.

Contents

  1. The parts at a glance
  2. Exponential Intelligence (expai)
  3. The REST API
  4. expservices and ezjscore
  5. The audit trail
  6. The help system for agents
  7. What is not part of Exponential today
  8. How to check your own installation

The parts at a glance

PartShips with the root repositoryActive after a new installationSends anything to an AI provider
Exponential Intelligence (expai)Yes: composer.json requires se7enxweb/expaiYes, for the administration siteaccesses, but idle until a provider key or a local model is configuredOnly after you configure a provider
REST API v1 and v2Yes: kernelYes, with authentication required by defaultNo
expservicesYes: part of the default distributionCheck it: the whoami call answers, and expservices.ini [Services] Enabled is its master switchNo
ezjscoreYesYesNo
Audit trailYes: kernelYesNo
Help system and exp:helpYes: kernelYes, for roles with exphelp/readNo

The rule of thumb: nothing in Exponential talks to an AI provider until an administrator configures one. The other parts are interfaces that an AI agent of your choice can use, under the permissions of an account you choose.

Exponential Intelligence (expai)

A writing assistant inside the administration interface. Editors ask in plain language; the assistant reads what it needs (class definitions, the current content, the tree around it) and writes drafts as the signed-in editor. It never publishes on its own (README, expai feature page).

  • Where it is: extension/expai, the Composer package se7enxweb/expai, required by the root composer.json.
  • What a new installation does: the installer activates it for the administration siteaccesses, creates its tables and gives its policies to the Administrator role only.
  • What is left to you: a provider key in settings/override/expai.ini.append.php (or a local model), the cron parts expqueue and expai, and the policy expai/write for the editors who should use it.
  • Providers: Anthropic, any OpenAI-compatible service through one adapter, or a local open-weight model through Ollama (Providers and models).

Its own documentation, with every setting, lives in the expai repository and in the help center under Extensions when the extension is active.

The REST API

/api/ezp/v1 reads nodes, children, fields and objects; /api/ezp/v2 adds creating and removing a node. Every request runs as a user and checks that user's policies. An agent authenticates with an OAuth2 token or a personal API key (expk_...) limited by scopes (REST API for applications, Agents and the REST API).

expservices and ezjscore

ezjscore calls registered PHP functions over HTTP and answers in JSON (JSON endpoints with ezjscore). expservices builds on it and turns the administration's functions into over a thousand named services, each with an access rule and a write flag, callable with a personal token (Remote services with expservices, Agents and expservices).

A read service can also opt in to be a tool of the assistant (Service tools).

The audit trail

The kernel's tamper-evident audit trail records what accounts do, including every request, refusal and draft of the assistant in its own channel ai, and every API key and token event (The audit trail for AI).

The help system for agents

Every git-tracked page below doc/ is a help page, written in Markdown. An agent can search and read them from the command line with ./console exp:help search and ./console exp:help show, or read the Markdown files directly (Agent-friendly documentation).

What is not part of Exponential today

  • An MCP server for agents is not part of Exponential today. Agents use the REST API, expservices and the command line instead.
  • No AI model is built in; the assistant calls the providers you configure.
  • The assistant is not an API for other programs; it works inside the administration for signed-in editors.

How to check your own installation

QuestionHow
Is expai there and active?Dashboard > Exponential Intelligence in the administration, or the Extensions page under Setup
Is a provider configured?Setup > EI: Models (expai/models) shows "key present" or "No key", never the key
Which expservices exist?Setup > RAD (/setup/rad), or the shell client's catalog command
Does the REST API answer?A GET /api/ezp/v1/content/node/2 with a key (Agents and the REST API)
Which help pages mention a topic?./console exp:help search "<words>"

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x