Conversation flows cross user, service, and project-runtime boundaries. User-scoped calls use bearer auth. Control-plane calls to project runtimes use signed requests.Documentation Index
Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Boundaries
| Boundary | Check |
|---|---|
| Studio to API | JWT or API key auth, then conversation or project permissions |
| SSE run stream | Conversation access before event replay or follow |
| Project event WebSocket | Project access during upgrade |
| Direct conversation WebSocket | Conversation access during upgrade |
| Studio to veryfront-agent | Bearer token authentication |
| veryfront-agent to API | Forwarded bearer token for project and conversation operations |
| API to project runtime | Control-plane JWS in x-veryfront-control-plane-jws |
| Project runtime control-plane routes | JWS verification before list, stream, resume, and cancel |