- Docs
- Reference
- API
API
Read access to flows, usage, and policy for your own dashboards and exports.
The API is read-focused: it's for pulling usage, flow, and policy data into your own tools, not for routing requests directly. Routing always happens through a connected desk.
terminal
Copycurl https://api.verybear.com/v1/flows \
-H "Authorization: Bearer $VERYBEAR_TOKEN"Common endpoints
| Endpoint | Returns |
|---|---|
| GET /v1/flows | All flows, with status, spend, and quality signal. |
| GET /v1/teams | Teams with budget and 30-day spend. |
| GET /v1/usage | Request-level usage, aggregated by flow and team. |
| GET /v1/policy | Current policy revision: approved models, blocked types. |
Tokens are scoped per seat and inherit that person's role. An API token for a team member can't read org-wide spend. Create and manage tokens from Organization → API tokens.
Available on Business and Enterprise plans. Enterprise additionally supports audit log export and SIEM streaming.
On this page
