Model providers
Route generation, reasoning, coding, multimodal, and retrieval steps across the providers approved for the deployment.
Connect the providers and tools Modeus can use.
Modeus can route a task step to an approved AI provider, file source, browser action, or business tool. Availability and access depend on the connections and permissions configured for the deployment.
Connection types
Each connection has a specific job.
A connection can provide context, run a model, perform a permitted action, or verify a result.
Reason
Files and knowledge
Use selected documents, repositories, structured data, and workspace memory without replaying unrelated history.
Browser and desktop tools
Carry out permitted navigation, data entry, collection, and local work with user-visible boundaries.
Business systems
Read or write approved records where a connector, account permission, and workflow policy allow it.
Verification systems
Run tests, queries, checks, or comparisons that can prove whether the finished result meets its definition of done.
Connection lifecycle
Access is limited by the connection and task.
Connecting a service does not give Modeus unrestricted access. The configured capability, account scope, workspace, and workflow rules determine what it can read or change.
- Authorize
Connect an approved account or tool.
Authentication and scopes should identify what the connection can read or change.
- Scope
Tie access to a workspace or workflow.
Modeus receives the context needed for the task rather than a vague permanent mandate.
- Use
Route the relevant step.
The system records the source, model or tool, action, and result that moved the task forward.
- Review
Inspect sensitive or consequential actions.
Review requirements depend on the operation, deployment policy, and system-of-record boundary.
- Revoke
Remove access when it is no longer needed.
Connection removal should stop future use; product-specific retention behavior must match the deployed service.
Evaluate a connection
Ask what it can do and what it cannot.
A responsible integration page distinguishes capability from availability and authorization from execution.
Supported operation
Read, write, search, execute, or verify, named precisely.
Deployment status
Provider and system support can vary by plan, region, and configuration.
Authorized scope
The connected account and granted scopes bound the available action.
Recorded result
The source and outcome stay connected to the task that used them.
Bring your actual systems