Skip to main content

Documentation Index

Fetch the complete documentation index at: https://agent37.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

A template is a prebuilt image that decides which agents an instance runs. Pass template when you create an instance, or omit it for the default.

​
Available templates

TemplateAgents installedAvailability
hermesHermes, general agent: browser, code, files.Default, available today
claude-codeClaude Code, for software work.Coming soon
codexCodex, for software work.Coming soon
openclawOpenClaw.Coming soon
allHermes, Claude Code, Codex, and OpenClaw together.Coming soon
curl
curl -X POST https://api.agent37.com/v1/instances \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "template": "hermes" }'
Omit template and you get hermes.
Multi-agent templates. When a template installs more than one agent (like all), a session runs whichever you choose with the agent field on its first message. The choice is fixed for the session’s life. Single-agent templates ignore it.

​
Custom templates

Custom templates are in preview, and for now they start from a public image you host. Build an image FROM our base, push it to a public registry you already use, then register it with us and create instances from it. Private images and pushing straight to our own registry are coming soon.
A custom template is your own image, built on our base and registered with us under a name you choose. Use it to preinstall skills, plugins, and packages so every instance you create from it starts ready.
1

Build on our base

Write a Dockerfile that starts FROM ghcr.io/agent37/base:latest and layer your skills, plugins, and packages on top. The runtime, gateway, terminal, desktop, file browser, and managed auth all come from the base and keep working; the container has passwordless sudo, so you can install anything. See Skills & plugins for the full Dockerfile.
docker build --platform=linux/amd64 -t my-agent:v1 .
Build for linux/amd64 even on an Apple Silicon Mac. Instances run on amd64, and an arm64 image will fail to start.
2

Push it to a public registry

Push the image to any registry you already use, such as Docker Hub or GitHub Container Registry, and make sure it is public so we can pull it. You log in to your own registry the usual way; we never see your registry password.
docker tag my-agent:v1 ghcr.io/your-name/my-agent:v1
docker push ghcr.io/your-name/my-agent:v1
3

Register it with us

Tell us the image to pull and a name to call it. The template moves from pending to ready, or failed with a reason if we cannot pull it (a wrong reference, a missing tag, or a private image).
curl
curl -X POST https://api.agent37.com/v1/templates \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "name": "my-agent", "image": "ghcr.io/your-name/my-agent:v1" }'
4

Create instances from it

Once the template is ready, pass the name you registered (or its tmpl_ id) as template when you create an instance.
curl
curl -X POST https://api.agent37.com/v1/instances \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "template": "my-agent" }'

​
Manage templates

ActionEndpoint
List built-in and custom templatesGET /v1/templates
Get one, to poll statusGET /v1/templates/{id}
Register an image you hostPOST /v1/templates
Delete a custom templateDELETE /v1/templates/{id}
​
id
string
The template id, prefixed tmpl_.
​
name
string
The name you chose, and what you pass as template when creating an instance, e.g. my-agent.
​
image
string
The image we pull, e.g. ghcr.io/your-name/my-agent:v1. Pin a tag; do not rely on latest.
​
status
string
pending while we pull and check the image, then ready, or failed with a reason if we cannot pull it.
Building FROM our base is what gives an instance the managed agent, chat, terminal, desktop, and files. An image that is not built from our base still runs, but as a plain container without them.
Coming soon. Registering a private image (you give us a read-only pull token for your registry) and pushing an image straight to our registry at registry.agent37.com, so you can skip hosting it yourself. For now, use a public image.

​
Next steps

Instances

Create an instance from a template, then size and manage it.

Send a message

Pick an agent with the agent field on a multi-agent template.

Skills & plugins

Preinstall skills and tools so every instance boots with them.