Autonomous Agent CLIs¶
Run autonomous agent CLIs against Amazon Bedrock models with stdapi.ai, using the same provider configuration you would point at OpenAI or Anthropic directly—only the base URL changes.
About Autonomous Agent CLIs¶
Unlike IDE coding assistants, autonomous agent CLIs plan and execute multi-step tasks on their own—reading files, calling tools, and iterating toward a goal without a human approving each step. They typically run on infrastructure you control (a server, a container, a scheduled job) rather than inside an editor.
What you can build:
- Personal assistants - Agents that read, search, and act on your behalf from the command line
- Autonomous research and task loops - Multi-turn tool-calling sessions that run unattended
- Self-hosted agent backends - CLIs wired into cron jobs, CI pipelines, or your own orchestration
Why Autonomous Agent CLIs + stdapi.ai?¶
-
No Vendor Lock-In
Point the CLI's existing OpenAI- or Anthropic-compatible provider settings at stdapi.ai—no fork, no plugin, no custom integration. -
Access Amazon Bedrock Models
Claude, Nova, DeepSeek, Qwen, and 100+ models, driven through the same agent loop your CLI already runs. -
Data Stays in Your AWS Account
Every tool call and model response is processed inside your own Bedrock deployment, never shared with a third-party AI cloud. -
Pay-Per-Use Pricing
No per-seat or per-agent licensing. Pay only Amazon Bedrock rates for the calls the agent actually makes.
%%{init: {'flowchart': {'htmlLabels': true}} }%%
flowchart LR
agent["Autonomous Agent CLI\n(Hermes, OpenClaw)"] --> stdapi["<img src='../styles/logo.svg' style='height:64px;width:auto;vertical-align:middle;' /> stdapi.ai"]
stdapi --> bedrock["<img src='../styles/logo_amazon_bedrock.svg' style='height:64px;width:auto;vertical-align:middle;' /> Amazon Bedrock"]
Prerequisites¶
What You'll Need
- ✓ stdapi.ai deployed - See deployment guide or run locally with Docker
- ✓ Your stdapi.ai URL - e.g.,
https://api.example.comorhttp://localhost:8000for local - ✓ Your API key - From Terraform output or configuration (optional for local development)
Hermes¶
Hermes (PyPI package hermes-agent) is an autonomous agent CLI written in Python.
Configuration¶
The simplest setup points Hermes at stdapi.ai through the same environment variables an OpenAI-compatible client would use:
export OPENAI_API_KEY=YOUR_STDAPI_KEY
export OPENAI_BASE_URL=https://YOUR_STDAPI_URL/v1
To select a specific wire format or model, declare a provider in Hermes' config.yaml instead:
providers:
stdapi:
name: stdapi.ai
api: https://YOUR_STDAPI_URL/v1
key_env: STDAPI_API_KEY
transport: chat_completions
default_model: anthropic.claude-fable-5
model:
provider: stdapi
model: anthropic.claude-fable-5
key_env names the environment variable Hermes reads the API key from—set STDAPI_API_KEY (or whatever name you choose) to your stdapi.ai key.
Transport Selection¶
transport is the standout setting: it picks which of stdapi.ai's three chat dialects the provider speaks, and api has to match the route serving it:
transport |
api base URL |
API |
|---|---|---|
chat_completions |
https://YOUR_STDAPI_URL/v1 |
Chat Completions |
codex_responses |
https://YOUR_STDAPI_URL/v1 |
Responses |
anthropic_messages |
https://YOUR_STDAPI_URL/anthropic |
Anthropic Messages |
Declare more than one entry under providers to reach more than one route side by side.
Anthropic Prompt-Caching Breakpoints¶
On the anthropic_messages transport, Hermes automatically places prompt-caching breakpoints on the system prompt and recent messages when the target model is Claude-named. Choose the cache lifetime with prompt_caching.cache_ttl:
prompt_caching:
cache_ttl: 1h # or "5m" (the default)
Only 5m and 1h are accepted—any other value is ignored. This pairs directly with stdapi.ai's own Anthropic Messages prompt-caching support: Hermes' breakpoints arrive as standard cache_control markers, which stdapi.ai translates into Bedrock cache points, up to the four the Converse API allows per request.
OpenClaw¶
OpenClaw doubles as a personal-assistant CLI and a coding agent. Its stdapi.ai configuration—onboarding wizard, the --custom-compatibility wire-format switch, and model selection—is documented once, in the AI Coding Assistants guide, and applies the same way whether OpenClaw is driving a coding task or a general assistant task.
Next Steps¶
- Getting Started — Deploy stdapi.ai to AWS with Terraform
- Local Development — Run stdapi.ai locally with Docker
- Python Client Libraries — Configuring LangChain and pydantic-ai directly against stdapi.ai
- More Use Cases — Explore other integrations and tools