Contact Gobare
How to reach the people who build Gobare, report a problem with the API, or get an integration question answered. Every channel below is monitored by the team that writes the code.
Support and integration questions
The fastest route for anything about the Agent API — an endpoint behaving unexpectedly, an integration that will not complete, a question the documentation does not answer — is the Discord server. It is read by the people who build the product rather than by a support tier, and questions there are usually answered with a specific answer or a specific bug.
If you are hitting an error from the API, include the request_id from the error body or the x-request-id response header. Every refusal the API makes carries one, and it is the difference between a report we can trace and a report we can only sympathise with.
- Discord: integration questions, bug reports, and release notes
- X: product announcements and what we are building
- pi on GitHub: issues with the agent itself, which is open source
Security
If you believe you have found a vulnerability, please report it privately through a Discord direct message to the team rather than in a public channel, and give us a way to reach you for follow-up. Please do not test against other tenants’ sessions or data; a sandbox of your own is free to create and is the right place to demonstrate an issue.
Accounts and billing
Account, key and project questions are answered in the Console, which is also where an API key is minted and where every session your code creates can be inspected — the same transcript, the same events, the same machine. Model spend is not billed by Gobare at all: you hold the provider key and the provider bills you directly, so a question about token cost is a question for your model vendor.