<!-- Generated from public website sources; do not edit this file. -->

> DSSUB design reference. Account, payments and API are not connected; prices, policies and setup examples require independent launch verification.

# Hermes Agent
Add a named DSSUB provider to the active Hermes profile.

## Current availability
DSSUB is a design preview. These are complete configuration references, not a live connection: `api.dssub.invalid` is intentionally non-routable. No real account, key, payment or inference service is connected. Replace the endpoint and use an authorized key only after DSSUB publishes verified connection details. Client versions and live tool compatibility remain unverified.

## Install and select a profile
Follow the [Hermes installation guide](https://hermes-agent.nousresearch.com/docs/getting-started/installation). Use the profile you intend to run. The default files are `~/.hermes/config.yaml` and `~/.hermes/.env`; named profiles have their own files.

## Save configuration and key
Merge the downloaded `config.yaml` into the active profile. Add the placeholder in `env.example` to that profile’s private `.env` only when replacing it with an authorized key. Keep the private file out of version control.

```yaml
# Merge with the config.yaml for your active Hermes profile.
providers:
  dssub:
    name: DSSUB preview
    api: https://api.dssub.invalid/v1
    key_env: DSSUB_API_KEY
    models:
      deepseek-flash: {}
      deepseek-v4-pro: {}
model:
  default: deepseek-flash
  provider: custom:dssub
```

```text
DSSUB_API_KEY=YOUR_DSSUB_API_KEY
```

## Start Hermes
```sh
hermes
```

Alternatively, `hermes model` opens the provider wizard. A custom endpoint uses the base ending in `/v1` and Chat Completions. Keep the saved credential, provider and model in the same profile.

## Switch models
Use `/model custom:dssub:deepseek-v4-pro` or `/model custom:dssub:deepseek-flash` in the session. Recheck the active profile if another endpoint responds.

## Choose reasoning effort
Use the client’s `/reasoning` controls only after the DSSUB route publishes supported settings. This template intentionally has no reasoning override. A client default or displayed level is not evidence that the gateway accepts the field.

## Verify your first request
After a live connection is published, start a new session in a small test project. First ask for a short text reply. Then ask the tool to read README.md and summarize it without modifying files. Confirm the selected provider and model, then match the request in [Usage](/account/usage). Check tool results, streaming completion and billed tokens separately. The current sample dashboard cannot verify a real request.

## Troubleshoot and restore
A DNS failure for `api.dssub.invalid` is expected in this preview. For a real connection, check the exact endpoint, API format, model ID and credential. A 401 concerns authentication; a 404 may concern a path or model; a 429 may concern a quota or rate limit. See [troubleshooting](/docs/error-codes/index.md).

Back up configuration before editing, merge only DSSUB fields, and retain your existing providers and permissions. To revert, select your previous provider and restore only the fields you changed. Stop and restart the tool after changing its startup environment.

## Reference
[Hermes provider documentation](https://hermes-agent.nousresearch.com/docs/integrations/providers/) and [reasoning configuration](https://hermes-agent.nousresearch.com/docs/user-guide/configuration#reasoning-effort), reviewed November 16, 2026.

---

HTML source: [Hermes Agent — dssub Tutorials](/docs/hermes/)
