Appearance
Integrations
Integrations in Modulos are built around clear boundaries: service access scoped to an AI System, user-level OAuth access, and API access for automation.
Choose the right integration
| You want to… | Use | Why |
|---|---|---|
| Power tests and continuous monitoring | Sources | Sources are service accounts attached to an AI System, designed for reliable, shared automation |
| Let Scout search and retrieve external context | Scout Connectors | Connectors are user-scoped and only see what the connected user can access |
| Access the Modulos API from code and tooling | API tokens | Tokens let scripts authenticate as a user without interactive login |
Rule of thumb
If it should keep working when people change teams, use a Source. If it should only see what a specific person can see, use a Connector. If it’s a script, use an API token.
The three integration primitives
| Primitive | What it connects | Where it’s managed | Scope |
|---|---|---|---|
| Sources | Service accounts and machine-to-machine integrations | AI System → Settings → Sources | One AI System |
| Scout Connectors | User accounts via OAuth | User Settings → Connectors | One user |
| API tokens | User tokens for API access | User Settings → API Tokens | One user |
Sources
Sources are service accounts attached to an AI System. They are used to power Runtime Inspection and other automation scoped to that AI System.
Scout Connectors
Connectors are user-level accounts connected to a specific user, usually via OAuth. They are used to bring user-scoped external context into Scout.
API tokens
API tokens are per-user bearer tokens used for programmatic access to the Modulos API.