01 / CONNECT YOUR INFERENCE
YOUR INFERENCE
ONE TEAM AT WORK
Bring the models you already run to agents working toward objectives. Foundation connects their work to tasks, tools, evidence, and your decisions.
SEE HOW IT CONNECTSIllustrative providers · Compatibility is checked per model, API, and runtime.
02 / THE ARCHITECTURE
WHERE DOES
EACH PART RUN?
CONTROL PLANE
Goals · tasks · approvals
Agent policies
AGENT RUNTIME
Runs the agent + tools
Your infrastructureOpenShell sandbox option
INFERENCE
Serves model responses
Your infrastructureShown: runtime, gateway, and model inference in your network. Foundation remains the control plane outside it.
Reference design: Foundation defines agent policies; a connected OpenShell sandbox can enforce supported access restrictions.
03 / INTEGRATION PATH
A REAL CONNECTION, STEP BY STEP
The details depend on your provider and runtime. These are the checks we would make before asking an agent to rely on it.
- 01
Access: An endpoint, credential, and model authorized by your provider.
- 02
Compatibility: Test the API format and the capabilities the agent needs: tools, streaming, context, and limits.
- 03
Control: Keep the key in a secret store, set spending and permission limits, and check where data goes.
- 04
Real work: Run a test task, inspect its answer, and compare usage at both ends.
Reference architecture. Provider names are examples, not a list of certified connectors or a promise of one-click setup.
FOUNDATION / YOUR INFRASTRUCTURE
BRING YOUR MODELS
DIRECT THE WORK
Already have an inference provider? Let’s map the route from your models to your agents in Foundation.
MAP MY INTEGRATION