Connect Hermes Agent to Scenepond
Use Scenepond as the model provider for your Hermes agent.
Official integration documentation- API base URL
https://scenepond-api-production.up.railway.app/v1- API protocol
- OpenAI Chat Completions
- Model ID
YOUR_MODEL_ID· Use the exact catalog ID
Hermes Agent runs tasks from your terminal. Scenepond supplies the selected chat model; Hermes manages the agent session and tools.
This guide assumes the client is installed and can start locally. You also need a Scenepond account, an enabled chat model, an API key with access, and sufficient balance for your first request.
Client installation and first launch ↗Set up with your coding agent
Copy this setup brief to the coding agent you already use. It contains the endpoint and instructions, without your API key. You can also follow the manual steps below.
Help me connect Hermes Agent to Scenepond using its custom provider. Scenepond guide: https://open.scenepond.ai/en/integrations/hermes Official integration documentation: https://hermes-agent.nousresearch.com/docs/integrations/providers#named-custom-providers API base URL: https://scenepond-api-production.up.railway.app/v1 Model ID: YOUR_MODEL_ID API protocol: OpenAI Chat Completions Inspect the installed client version and existing configuration first. Preserve other providers, agents, channels, and settings. Replace YOUR_MODEL_ID only with an enabled Scenepond model permitted by my API key. Verify tool support and actual context limits; do not invent capabilities. I will set the raw key in SCENEPOND_API_KEY or the client’s secure credential field. Do not ask me to paste it into this conversation, print it, commit it, or embed it in browser code. Follow the Scenepond guide for this client’s provider syntax and secret handling. Use the /v1 base URL and chat completions protocol with Scenepond credentials, rather than upstream provider credentials. Validate configuration locally first. Ask before making a paid API request. If a model or credential is missing, explain what I need to configure. Do not retry requests automatically. Report the changed settings, how to start a fresh session, and what has and has not been verified.
1. Prepare your model and API key
Copy an enabled model ID from the catalog and create a Scenepond API key with access to it. Agent tasks need a model with verified tool-calling support; check context limits and supported protocols before choosing.
Replace YOUR_MODEL_ID with the exact configured ID. These instructions configure a chat endpoint; they do not enable image or video generation tools. Model access and successful calls depend on backend configuration and account balance.
2. Configure the custom provider
In your existing ~/.hermes/config.yaml, merge this named provider and model selection. Keep any other providers and settings.
1providers:
2 scenepond:
3 api: "https://scenepond-api-production.up.railway.app/v1"
4 key_env: "SCENEPOND_API_KEY"
5 transport: "chat_completions"
6
7model:
8 provider: "custom:scenepond"
9 default: "YOUR_MODEL_ID"Store the raw Scenepond API key in ~/.hermes/.env using SCENEPOND_API_KEY. Do not include a Bearer prefix.
SCENEPOND_API_KEY=YOUR_SCENEPOND_API_KEYHermes requires a model with at least 64,000 context tokens. Set a context length only when the model actually supports it; configuration cannot increase its capacity.
3. Start a new session
hermesStart a fresh session after saving. Existing Hermes sessions keep their selected model until you switch it. You can also configure a custom endpoint interactively with hermes model.
4. Confirm the response and usage
Confirm that the client has selected your Scenepond provider and exact model ID. Send this short message in a new session; the request uses your account balance.
Reply READY without using tools.Check that a text reply arrives, then open Scenepond usage records and match the model and request time. Review the actual settled charge. A text reply verifies basic chat access; test tools and reasoning separately only when the model supports them.
Common setup issues
- Missing key or rejected credentials
- Check that the running client can read the raw key and that the Scenepond key is enabled. Keep the secret out of diagnostic output.
- Model unavailable
- Check the exact catalog ID, key permissions, and balance. For OpenClaw, the model reference also needs the scenepond/ prefix.
- Hermes context error
- Choose a model that actually supports at least 64,000 context tokens. Increasing a configuration value cannot extend the model’s capacity.
- Chat works, tools fail
- Check the selected model’s tool support and the client’s tool settings. Successful text chat does not establish support for every agent capability.