Skip to main content
Supplied Actions are pre-built, Maitai-maintained capabilities you can add to any agent in one click, no configuration, no credentials. Adding one clones it onto your agent as a normal action you fully own.

​
Current catalog

The catalog grows over time, check the portal or API for the live list.

​
Adding from the portal

On your agent’s page, open Add Capability and choose Supplied by Maitai. Pick an action and add it. A lock icon indicates the action uses Maitai-managed credentials. If your agent already has an action with the same name, you’ll see an “already added” notice instead of a duplicate.

​
Adding via API / CLI

List the catalog:
Each entry includes id (the catalog action id), action_name, action_type, description, and uses_platform_credentials. Clone one onto your agent:
Returns the newly created action (201). A 409 means the agent already has an action with that name.

​
After adding

The clone is yours, it behaves like any other capability:
  • Edit the prompt, schema, or usage guidance; disable or delete it at will.
  • It lands on your agent’s draft. Publish the action and a new agent version, then point a release at it, before it serves traffic.
  • The clone’s meta.supplied block records which catalog entry (and version) it came from.
Catalog entries themselves are read-only, adding always clones, so later edits to your copy never affect the catalog (and vice versa).

​
Maitai-managed credentials

Some supplied actions (like Web Search) call third-party APIs with Maitai-owned keys. These reference a {{platform.NAME}} token in their auth config:
  • The token resolves server-side at execution time: the raw key never appears in your action config, API responses, or the portal.
  • Tokens are host-pinned: the credential only resolves when the request targets the intended provider. Re-pointing the action at another host fails the call rather than exposing the key.
  • You never supply these values, unlike per-request secrets, there’s nothing to pass at request time.
To call a different provider with your own credentials, build a regular API Action instead.