InferenceCustom Endpoints

Set Up an Anthropic-Compatible Endpoint

View as Markdown

Use the custom Anthropic-compatible provider to configure a custom base URL and model with COMPATIBLE_ANTHROPIC_API_KEY. The runtime API differs by agent capability.

Run Onboarding

Start the onboard wizard.

$nemohermes onboard

Select Other Anthropic-compatible endpoint. Enter the endpoint base URL, model ID, and API key when prompted. Use any non-empty placeholder such as dummy when the endpoint does not require authentication.

Understand Hermes Routing

Hermes uses the managed OpenAI Chat Completions frontend at https://inference.local/v1 for this provider. NemoClaw validates /v1/chat/completions, verifies the same path during inference setup, and registers it with OpenShell as type=openai using OPENAI_BASE_URL. The route keeps COMPATIBLE_ANTHROPIC_API_KEY as its credential binding.

This path avoids duplicate Anthropic SSE message_start events. If the endpoint only implements Anthropic Messages, onboarding stops instead of creating a Hermes sandbox with an unusable runtime route.

OpenClaw custom Anthropic routes and first-party Anthropic routes remain on the native Anthropic Messages frontend. AWS Bedrock routes keep their existing OpenAI-compatible adapter behavior.

Run Non-Interactive Onboarding

Set NEMOCLAW_PROVIDER=anthropicCompatible and provide the endpoint URL, model, and credential.

$NEMOCLAW_PROVIDER=anthropicCompatible \
>  NEMOCLAW_ENDPOINT_URL=http://localhost:8080 \
>  NEMOCLAW_MODEL=my-model \
>  COMPATIBLE_ANTHROPIC_API_KEY=dummy \
>  nemohermes onboard --non-interactive