Based on the tool’s documented custom-provider setup. Live AsterWise compatibility has not yet been tested for this tool.
Which API does this use?
This guide selects Chat Completions through the custom endpoint’schat_completions transport. The base URL is https://api.asterwise.dev/v1. The client builds the full endpoint: https://api.asterwise.dev/v1/chat/completions.
The model name chooses AsterCode or AsterWork, not the protocol. Use the base URL in the configuration below, rather than the full endpoint.
1. Open the provider wizard
Exit any running chat and run:2. Choose a custom endpoint
Select Custom endpoint and enter:
If the wizard asks for an API format, select Chat Completions. In current provider configuration this is
transport: chat_completions. Save the configuration. Use aster-work instead if you prefer AsterWork.
3. Start a new session
hermes model to change provider settings; the in-chat /model command is not the initial provider setup wizard.
Hermes can configure auxiliary models separately. Check those settings if background tasks use a different provider from your main chat. AsterWise’s API key does not configure separate search or other external services.
Check the connection
Ask “Reply with hello” first. Confirm a response appears and find the request in Usage in AsterWise. Then try a small coding task before a larger project. For authentication errors, runhermes model again, check the saved custom endpoint and key, then start a new session. See troubleshooting.