Atlas SDK follows a simple promise: your agent, our orchestration. Adapters create a small, consistent interface so you can place the adaptive dual-agent loop (student + verifying teacher) on top of nearly anything—from hosted APIs to local Python functions.Documentation Index
Fetch the complete documentation index at: https://docs.arc.computer/llms.txt
Use this file to discover all available pages before exploring further.
Choosing an Adapter
| Adapter | Use when… | Strengths | Things to watch |
|---|---|---|---|
litellm | You need multi-provider support or want future-proof compatibility. | Supports 100+ LLM providers, minimal setup, native tool calling, streaming support. | Recommended for all new projects. |
http_api | Your agent already runs behind an HTTP endpoint. | Language-agnostic, deploy-anywhere. | You define the payload schema, handle auth, and parse responses. |
python | You want to call local functions or LangChain runnables directly. | Lowest latency, easy debugging. | Runs inside the orchestrator process—ensure your code is safe and performant. |
LiteLLM Adapter (atlas/connectors/litellm.py)
This is the recommended adapter for all LLM providers, supporting 100+ models via LiteLLM.
- Supports conversation history and tool call metadata automatically.
- Accepts
response_formatfor JSON mode. - Works with OpenAI, Anthropic Claude, Google Gemini, XAI Grok, Azure OpenAI, AWS Bedrock, and local models (Ollama, vLLM).
HTTP Adapter
For microservices or non-Python agents. Settype: http_api, provide transport.base_url, and define payload_template + result_path. See Configuration Reference for details.
Python Adapter
For local functions or LangGraph runnables. Settype: python, specify import_path and attribute. Supports async/sync callables and generators. See Configuration Reference for details.
Building Custom Adapters
All adapters share a minimal interface (AgentAdapter). To add a new one (e.g., for gRPC), follow these steps:
- Extend the
AdapterTypeenum inatlas/config/models.py. - Implement a class inheriting from
AgentAdapter. - Register it with
register_adapter(seeatlas.connectors.registry) and import the module fromatlas.connectors.__init__so it auto-registers at runtime.
http_api adapter and swapping the transport layer.
Atlas auto-imports built-in adapters via
atlas.connectors.__init__. Custom adapters should follow the same pattern—expose your module there (or import it in your app startup) so registration runs once on load.Structured Payloads
Pass complex nested dictionaries as tasks without serialization overhead:Learning Tracking
Integrate learning tracking into custom adapters:resolve_playbook(), detect_and_record(), record_action_adoption(), record_session_outcome(). See Learning System for details.
Migrating from OpenAI to LiteLLM Adapter
Changetype: openai to type: litellm in your config. The litellm adapter is a drop-in replacement with no breaking changes. Benefits include multi-provider support, local model compatibility, and elimination of deprecation warnings.
Decision Checklist
| Need | Recommendation |
|---|---|
| Fastest time-to-first-run | litellm adapter with any provider. |
| Reuse an existing microservice | http_api adapter with proper retries and auth. |
| Full control in local experiments | python adapter calling your local function. |
| Access any LLM provider (OpenAI, Claude, Gemini, etc.) | Use litellm adapter with the appropriate provider setting. |
Next Steps
- Configure the rest of the runtime in
SDK Configuration. - See how the orchestrator uses your adapter in
How Orchestration Works. - Understand the dual-agent reasoning concept in
Adaptive Dual-Agent Reasoning.