Click to enlarge Provider runtime overview
The provider keeps auth, skills, scripts, and downstream execution inside one explicit boundary.
An integration architecture for enterprise systems, not just tool connectors.
AtlasClaw turns integrations into provider contracts so IM, web, embedded apps, and webhook calls can reach one agent layer, execute skills, and interact with governed enterprise systems.
Provider runtime
Start with the provider runtime architecture.
This diagram shows more clearly how auth, skills, scripts, and downstream system execution are held inside the provider boundary.
Click to enlarge Provider runtime overview
Close preview The provider keeps auth, skills, scripts, and downstream execution inside one explicit boundary.
Why this architecture
Integration is where enterprise AI either becomes reliable or falls apart.
AtlasClaw is designed so integrations stay explicit. Providers hold system contracts, skills stay executable and narrow, and the core keeps one reusable orchestration model.
Provider contracts, not loose tool wrappers
Each integration owns its auth model, scripts, references, and system-specific rules instead of leaking them into the core.
Skills become controlled system verbs
Skills are the governed execution boundary between user intent and target-system action.
One agent layer across many access channels
IM, web, embedded modules, and webhook callers can all reach the same AtlasClaw execution model.
Existing systems gain AI without being rebuilt
Traditional products can call AtlasClaw as an AI layer instead of implementing their own agent stack from scratch.
Execution path
From access channel to governed system action.
The integration model stays readable because every hop has a clear responsibility boundary.
- Users or systems reach AtlasClaw through IM, web UI, embedded panels, or webhook entrypoints.
- The agent engine selects provider-qualified skills and builds the execution plan.
- Providers translate intent into target-system operations with the right auth and data boundaries.
- Enterprise systems remain the operational source of truth for permissions, workflow state, and audit.
Integration method
Provider model
A provider is a self-contained integration package: connection contract, auth conventions, skills, scripts, and reference material. The core loads providers from `providers_root` and exposes provider-qualified skills for runtime dispatch.
- Providers keep platform-specific auth and workflow logic out of the core.
- Skills stay readable for users while remaining explicit for runtime dispatch.
- Webhook and channel access can target the same provider-qualified execution layer.
Architecture value
What the enterprise gets
This model is not just about connecting APIs. It creates one governed AI execution layer above existing systems.
- One multi-user agent layer instead of repeated personal integrations.
- A reusable way to add AI capability into existing enterprise products.
- Clearer boundaries for access control, audit, and system ownership.
Enterprise domains
One provider model across the enterprise stack.
The same integration architecture can be applied across operational systems, business systems, and developer systems.
SmartCMP
A strong provider reference showing request flows, approvals, webhook orchestration, and business-facing skill layers.
View referenceJira
A concrete provider example for issue operations and provider wiring patterns.
View referenceITSM systems
Service and request workflows can be executed through governed providers instead of ad hoc tool calls.
Monitoring and alerting systems
Alerts, incidents, and operational diagnostics can be exposed as explicit skills.
OA, CRM, HR, and finance systems
Business-side workflows can gain AI coordination while keeping system-side permissions and approvals intact.
GitHub and engineering tools
Development workflows can be integrated as provider domains instead of bolted-on personal-agent tools.
Build next
Read provider docs Build your own provider
Use the SmartCMP and Jira examples as reference points, then package your own platform with provider-level config, skill metadata, and narrow scripts. Contributions of new system integrations are welcome in the atlasclaw-providers repository.