Embed Opisense agents in your stack.
The Opisense Developer API exposes org-scoped REST endpoints for agents, workflows, tools, and memory—the same governed execution layer as Workspace, called from your own products and automations.
Discover org agents before embedding
Discover org agents before embedding
Teams integrate Opisense where their customers and operators already work.
Programmatic access to governed execution
Call catalog and custom agents, start workflows, execute tools, and read memory threads—under the same org auth and policy as Workspace.
Agents—generate and stream
List org agents, send messages, and receive completions or streamed responses. Catalog specialists and custom agents you build in Workspace are available through the same API.
Discover org agents before embedding
Discover org agents before embedding
Workflows and tools
Start workflow runs with structured input, list available tools, and execute them programmatically—wire Opisense into CRM updates, ticket routing, or internal ops scripts.
Discover org agents before embedding
Discover org agents before embedding
Memory and governance
List memory threads and continue conversations across sessions. Requests are org-authenticated; actions respect the same role-based policy and audit expectations as Workspace.
Discover org agents before embedding
Discover org agents before embedding
What the API gives your product
Ship AI features in your product without rebuilding agents, tools, or policy from scratch.
Standard HTTP endpoints with JSON payloads—integrate from any stack.
Authenticated per workspace; agents and tools match what admins configure.
OpenAPI reference with try-it-out examples at the API server.
REST API for agents, workflows, tools, and memory—embed Opisense execution in your products and automations. Your product keeps the UX; Opisense keeps execution inside policy—with the same agents your operators trust in Workspace.
Opisense team
Governed execution for enterprise operations
Quick answers
Build on Opisense execution.
Book a demo to map API integration to your stack—or open the OpenAPI reference and start exploring endpoints.