Tools
Goose
Set up Goose with Cognitivers, then verify your connection.
Connects directly
Block's agent. Uses OPENAI_HOST rather than the OPENAI_BASE_URL name other tools use.
1. Before you begin
- Goose installed and ready to configure.
- A Cognitivers API key. See authentication and key management.
Configuration location
Environment variables, plus config.yaml for the model
Need an API key? Request access before running these examples.
2. Configure the connection
Apply the following configuration in the location above. Replace credential placeholders with your own key; keep secrets out of version control.
# The host goes without a trailing path: Goose appends the base path itself.
export OPENAI_HOST=https://api.cognitivers.com
export OPENAI_BASE_PATH=v1/chat/completions
export OPENAI_API_KEY=sk-cog-...
# ~/.config/goose/config.yaml
active_provider: openai
providers:
openai:
enabled: true
model: cog-pro
configured: trueCompatibility notes
- The variable is OPENAI_HOST, not OPENAI_BASE_URL, and OPENAI_BASE_PATH defaults to v1/chat/completions.
- Goose does not read provider keys from config.yaml. A key placed there is ignored and shows up later as an authentication error.
- For several endpoints at once, add a JSON file under custom_providers/ with engine set to openai.
3. Verify the setup
Use this prompt in your configured tool to check authentication, a response and streaming. It reports failures without printing your key.
Open verification prompt
You are working in a repository where I have configured Goose to use Cognitivers as its model provider.
The API is OpenAI-compatible chat completions.
- Base URL: https://api.cognitivers.com/v1
- Streaming: use the same base URL with stream: true
- Models: cog-fast (agents, pipelines, volume), cog-pro (one hard task), cog-embed (retrieval)
- Authentication: an API key in the Authorization header as "Bearer sk-cog-..."
Do these four things and then stop.
1. Check that the credential is present in my environment and tell me the name of the variable you found it in. Do not print the key itself, not even partially.
2. Send one non-streaming chat completion asking for a single short sentence, using cog-fast. Show me the exact command or code you used and the model's reply.
3. Send the same request with streaming enabled and confirm you received server-sent events, not one buffered body.
4. If any step fails, tell me the exact error, the status code and the request that produced it, then stop. Do not try more than two fixes, and do not change any configuration file without showing me the diff first.
Rules: never write the key into a file that is tracked by git, never print it in full, and if the request works, say so in one line instead of writing a report.
5. This client reads OPENAI_HOST and OPENAI_BASE_PATH rather than the variable name other tools use. Confirm which one it actually read, and remember that it ignores keys placed in config.yaml.If the check fails, use the reported status code in the error reference and review the compatibility notes above.