Local Development with Docker/Podman¶
Run stdapi.ai locally for development, testing, and evaluation using the free community container image (AGPL-3.0). Full API compatibility — the same endpoints and features as the production deployment.
New to Amazon Bedrock?
To run stdapi.ai locally you need:
- Docker or Podman installed
- An AWS account — create one free
- AWS credentials configured locally — via
aws configureoraws sso login(AWS CLI setup guide)
Run It¶
With AWS credentials (after aws sso login):
docker run --rm -p 8000:8000 \
-v ~/.aws:/home/nonroot/.aws:ro \
-e AWS_BEDROCK_REGIONS=us-east-1,us-west-2 \
-e ENABLE_DOCS=true \
ghcr.io/stdapi-ai/stdapi.ai-community:latest
With environment variables instead:
docker run --rm -p 8000:8000 \
-e AWS_ACCESS_KEY_ID=your-access-key-id \
-e AWS_SECRET_ACCESS_KEY=your-secret-access-key \
-e AWS_SESSION_TOKEN=your-session-token \
-e AWS_BEDROCK_REGIONS=us-east-1,us-west-2 \
-e ENABLE_DOCS=true \
ghcr.io/stdapi-ai/stdapi.ai-community:latest
Podman on Fedora/RHEL with SELinux
Add the :z SELinux label and --userns=keep-id:
podman run --rm -p 8000:8000 \
--userns=keep-id \
-v ~/.aws:/home/nonroot/.aws:ro,z \
-e AWS_BEDROCK_REGIONS=us-east-1,us-west-2 \
-e ENABLE_DOCS=true \
ghcr.io/stdapi-ai/stdapi.ai-community:latest
The :z flag relabels files for container access. Use :Z if multiple containers share the volume. --userns=keep-id maps your host user ID to the container user.
See also Troubleshooting → Podman volume mount fails on Fedora/RHEL with SELinux if you hit this after the fact.
%%{init: {'flowchart': {'htmlLabels': true}} }%%
flowchart LR
openai["<img src='../styles/logo_openai.svg' style='height:64px;width:auto;vertical-align:middle;' /> OpenAI SDK"] --> local["<img src='../styles/logo.svg' style='height:64px;width:auto;vertical-align:middle;' /> stdapi.ai (community)<br/>Docker/Podman"]
anthropic["<img src='../styles/logo_anthropic.svg' style='height:64px;width:auto;vertical-align:middle;' /> Anthropic SDK"] --> local
local --> bedrock["<img src='../styles/logo_amazon_bedrock.svg' style='height:64px;width:auto;vertical-align:middle;' /> Amazon Bedrock"]
local --> polly["<img src='../styles/logo_amazon_polly.svg' style='height:64px;width:auto;vertical-align:middle;' /> Amazon Polly"]
local --> transcribe["<img src='../styles/logo_amazon_transcribe.svg' style='height:64px;width:auto;vertical-align:middle;' /> Amazon Transcribe"]
local --> s3["<img src='../styles/logo_amazon_s3.svg' style='height:64px;width:auto;vertical-align:middle;' /> Amazon S3"]
Test It¶
# Check health
curl http://localhost:8000/health
# List all available models
curl http://localhost:8000/search_models
# Search models by capability (e.g. streaming-capable chat models only)
curl "http://localhost:8000/search_models?route=/v1/chat/completions&streaming=true"
# Chat completion
curl http://localhost:8000/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "amazon.nova-micro-v1:0",
"messages": [{"role": "user", "content": "Hello!"}]
}'
Interactive API docs: Open http://localhost:8000/docs for Swagger UI with all available endpoints.
Point an application at it: set the base_url (Python) / baseURL (Node.js) option to http://localhost:8000/v1 (OpenAI SDK) or http://localhost:8000/anthropic (Anthropic SDK), and set the model field to a model from the catalog above. No API key is required by default — pass any non-empty string if your client insists on one. The API Overview has SDK snippets for Python, Node.js, and more.
Try other models
amazon.nova-micro-v1:0 is a fast, low-cost model — great for confirming the pipeline works. Once you see a response, switch the model field to anthropic.claude-fable-5, anthropic.claude-sonnet-5, or any other Bedrock model available in your configured regions.
Use GET /search_models (shown above) to discover what's available and filter by capability, or GET /v1/models for strict OpenAI SDK compatibility — see the Search Models API reference.
Optional: expose the API as MCP tools
The MCP server is off by default. Add -e ENABLE_MCP_STREAMABLE_HTTP=true to the docker run command and every endpoint becomes a named MCP tool at http://localhost:8000/mcp, callable directly by Claude Code or any MCP client.
Every exposed tool adds its schema to each MCP client's context window, so expose only the tools you actually use — for example -e MCP_INCLUDE_TOOLS=openai_chat_completion,openai_embedding,search_models. See the MCP configuration reference.
Technical Notes¶
Building from source: See the Dockerfile if you prefer to build the image yourself.
Container runtime: Both community and Marketplace images use Granian, a high-performance Python ASGI server. Granian environment variables (e.g., GRANIAN_PORT, GRANIAN_WORKERS) are supported.
Configuration: See Configuration Reference for all environment variables.
Ready for Production?
When you're ready to deploy to AWS with HTTPS, auto-scaling, and enterprise features, the production deployment guide gets you running with two Terraform commands. The AWS Marketplace subscription includes a 14-day free trial of the license.
Next Steps¶
stdapi.ai works with any OpenAI or Anthropic-compatible tool. Here are popular integrations to try locally:
- Open WebUI — Private ChatGPT-like interface with RAG, multi-modal support, and document upload
- n8n Workflows — AI-powered automation with 400+ integrations
- AI Coding Assistants — Claude Code, Cline, OpenCode, Zed with Amazon Bedrock models
- API Overview — All endpoints, parameters, and usage examples
- Getting Started — Deploy the production stack on AWS with Terraform
- Troubleshooting — Podman/SELinux, auth, model-not-found, and other common errors