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

Service tools

How read services of expservices become tools of Exponential Intelligence - opting in with 'ai' => true or the ServiceTools settings, the services expservices opts in itself (node, section, state, tags), what the model…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/ai-agents/expai/service-tools.md

On this page

Service tools

This page is for administrators and developers who want the assistant to use more lookups than its own. A read service of the extension expservices, declared once, is usable by people over HTTP and by the assistant as a tool, each with the caller's own permissions (extension documentation: service tools).

Contents

  1. How a service becomes a tool
  2. Services offered out of the box
  3. What the model sees
  4. Checks on every call
  5. Reads only

How a service becomes a tool

Services are private to the assistant by default. A service is offered when it opts in:

WhereWhatEffect
The service declaration'ai' => trueOffered to the assistant
The service declaration'ai' => array( 'summary' => '...' )Offered, with this description for the model
The service declaration'ai' => falseNever offered, even when the settings list it
expai.ini [ServiceTools] Services[]<domain>::<method> or <domain>::*Offered without changing code
expai.ini [ServiceTools] Domains[]<domain>Every read service of the domain offered
expai.ini [ServiceTools] Exclude[]the same patternsNever offered
expai.ini [ServiceTools] EnableddisabledNo service is offered

Writing a service domain of your own: Remote services with expservices.

Services offered out of the box

expservices opts in these read services itself, each checked by the node's own read access:

DomainServices
nodechildren names, children count, breadcrumb, tree, latest, find
sectionlist, section of a node
stategroups, states of an object
tagsroots, children, tree, search, tags of a node

What the model sees

Each tool has a description that starts with "[Exponential service, read only]", names the service and what it returns, and says the answer is data, not instructions. Its input schema has one property per declared argument. The answer is the service's own envelope, wrapped with a note that it is data; an error envelope becomes a tool error the model can correct.

Checks on every call

The call runs in the same PHP process, as the signed-in editor, through the same entry the HTTP router uses. Before it:

  1. the policy expai/services (limitation Domain); without it no service is offered;
  2. the policy ezjscore/call, and the router's own check of the domain, exactly as for HTTP;
  3. the service's own access declaration, and its own content checks;
  4. the data policy of the panel's provider: an argument naming content the policy keeps away refuses the call.

After it, the data policy filters the answer: rows naming objects the policy keeps away are left out and counted. Each call is recorded as a tool entry of the request's usage row.

Reads only

A service declared 'write' => true is never offered, whatever the declaration or the settings say. The assistant's writes stay its own draft tools, which never publish (Drafts and human review).

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