Model providers
Connect local or hosted model runtimes through one contract, with model discovery, chat, streaming and declared capabilities.
Native extension model
Capabilities connect cleanly—and evolve independently.
AEP—Agentstration Extension Protocol—is Agentstration’s native extension model. It defines how the platform discovers, connects to and invokes capabilities running outside its core process, so each extension retains its own technology, lifecycle and failure boundary.
Agentstration Extension Protocol
AEP is Agentstration’s extension model.
The Agentstration Extension Protocol defines the native contract between the platform and its extension processes. It gives Agentstration a consistent way to discover capabilities, invoke them and observe their lifecycle without loading arbitrary plugins into the core process.
Discover
An extension describes its identity, version and capabilities.
Connect
Agentstration communicates with the extension through the AEP contract.
Invoke
Runtime work calls a declared capability with structured input.
Observe
Results, failures and health remain visible across the boundary.
What extensions can add
What extensions can add
Tools
Expose tools and their schemas to Agentstration. AEP tool contributions can rely on MCP for discovery and invocation.
Configuration
Publish versioned configuration schemas and secret annotations without hard-coding provider-specific fields into the platform.
Specialized capabilities
Add namespaced capabilities outside the core process and evolve them on their own lifecycle.
Build the system around your agents
From promising prototype to dependable platform.
Explore the architecture today. Connect to the project as public resources become available.