UARP
The runtime under Snaga.
Universal Agent Runtime Platform. Snaga is what you see; UARP is what runs underneath — the API, the protocols and the rules agents work under. Each item below is something you can call today.
Barista
Brings your tools into the conversation.
One workspace on every device
The web, the iOS and Android apps, and the Quark browser with Snaga Code inside it sign in to the same workspace: the same agents, the same connections, one history of runs. The native Mac app is being prepared for release, and the Windows app is in development.
Snaga Code on your machineA documented API
Agents, runs, sessions, knowledge, schedules and governance are reachable over one HTTP API, described in a public OpenAPI document. Keys carry scopes, and run events stream as they happen.
API referenceCompatible with the clients you have
Chat completions, responses, embeddings, a model list and messages, in the formats common client libraries already speak: an existing client works with UARP once it has a new base address and key.
Compatibility notesMCP in both directions
Agents use tools from the MCP servers you connect, and the workspace's own tools, resources and prompts are served to any MCP client from one address.
Agents other systems can discover
A published agent serves an A2A agent card at /.well-known/agent.json, or an OASF record with format=oasf, and takes tasks over A2A's JSON-RPC: send, stream, check and cancel.
Rules inside the runtime, not beside it
The constitution, per-tool human approval, a hash-chained ledger and the EU AI Act documents are part of the runtime every agent runs in.
What an institution gets
Snaga and UARP
Snaga is the product: the workspace, the app and Snaga Code. UARP is the platform under them, and developers meet its name in the API document, in key prefixes (uarp_…) and in headers. Both names are ours; they describe one system from two sides.