---
title: "Usage"
manual: "AI Universe"
version: "1.0"
permalink: "https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:usage@1.0"
source: "Usage/Index.rst"
rendered: "2026-10-19T14:06:07+00:00"
---

# Usage {#usage}

This guide focuses on practical operation for editors, administrators, and
non-technical stakeholders.

-   [For administrators](https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:for-administrators@1.0)
-   [For editors](https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:for-editors@1.0)
-   [For non-technical stakeholders](https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:for-non-technical-stakeholders@1.0)
-   [What to expect operationally](https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:what-to-expect-operationally@1.0)
-   [Known boundaries](https://docs.typo3.org/permalink/nitsan/ns-aiuniverse:known-boundaries@1.0)

## For administrators {#usage-admin}

Daily responsibilities:

-   Keep provider API keys valid.
-   Maintain default model settings.
-   Monitor OpenAI usage trends.
-   Keep credentials and access permissions under control.

### Admin checklist {#usage-admin-checklist}

1.  Confirm selected `defaultModel`.
1.  Confirm provider key is set (for selected provider).
1.  Test extension-dependent AI features in your connected modules.
1.  Review usage statistics regularly (cost/rate-control).

## For editors {#usage-editors}

Editors usually do not configure providers directly. They interact with
features built by other extensions that depend on AI Universe.

When AI features fail in a backend module:

-   Retry once.
-   Capture exact error text.
-   Inform administrator with module/page context.

## For non-technical stakeholders {#usage-non-technical}

AI Universe helps organizations by:

-   Reducing duplicated AI integration work across extensions.
-   Centralizing provider and model governance.
-   Improving consistency of AI capabilities across teams.

## What to expect operationally {#usage-expectations}

-   Some providers have rate limits and temporary outages.
-   Model behavior can differ between providers and versions.
-   Statistics data may be cached and not always real-time.

## Known boundaries {#usage-boundaries}

-   No standalone frontend plugin is provided by this extension.
-   This package is a service layer; UI features come from dependent extensions.