hermes - 💡(How to fix) Fix [Feature]: Support `service_tier` for Amazon Bedrock

Problem or Use Case

I am trying to use Hermes with Amazon Bedrock, migrating from OpenClaw. Most of my Bedrock models are configured to use service_tier=flex to reduce the API cost by 50%, trading a slightly worse latency for reduced cost. The flag does not seem to be honored by the Hermes Bedrock implementation.

Proposed Solution

Support the service_tier configuration for the Amazon Bedrock model provider. This flag must be configurable by model, since not all models support each possible value: priority, standard, flex, reserved. Those with reserved model capacity will rarely have that available across all models.

I did the implementation in OpenClaw, it was a small fix, with documentation as much of the PR as the code changes. Since it will likely require documentation changes, the change spans more than one file. And if you want to pull these values from OpenClaw during the migration, it requires even more changes.

Alternatives Considered

No response

Feature Type

Other

Scope

Small (single file, < 50 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)