Secrets remain controlled
Keep credentials and environment-specific configuration outside workflow prompts and application code.
Developers
Build the agent. Keep the production machinery out of your application.
Trigger stateful workflows through APIs, connect tools through MCP, stream progress, and inspect every execution without assembling a new control plane for each use case.
Backend-first
Your interface calls a workflow, not a chain of fragile services.
Keep the customer experience inside your product while AgentRuntime handles orchestration, state, tools, waits, retries, and intervention behind the API.
POST /v1/workflows/:workflow_id/runs
create-run.tsTypeScript
const run = await agentRuntime.runs.create({
workflowId: "customer-onboarding",
input: {
customerId: "cus_2048",
requestedBy: "product-api"
},
stream: true
});
for await (const event of run.events) {
console.log(event.step, event.status);
}Tools and MCP
Connect the systems where the work actually happens.
Give agents governed access to business software, internal services, and your own tools through a consistent execution layer.
Inputs and outputs remain explicit
Validate the contract between agents, tools, and downstream steps before the run continues.
Access follows the workflow
Control which tools, operations, and data boundaries are available for a particular execution context.
Execution lifecycle
Every run has an identity, history, and recovery path.
Trigger
Start from an API, webhook, schedule, product event, or human action.
Execute
Move through agents, tools, decisions, and parallel groups while maintaining state.
Wait
Pause for approval, external events, or future time and resume the same run later.
Observe
Stream events and inspect timelines, logs, traces, inputs, outputs, and dependencies.
Recover
Retry, redirect, or intervene without treating the whole process as an opaque request.
Build with your stack
Use AgentRuntime as infrastructure, not as a replacement for your product.
Go, TypeScript, and Python
Trigger workflows, inspect runs, and integrate execution into backend services.
Webhooks and streaming
Receive lifecycle events or stream live progress into your own interfaces.
Scoped access
Use application and run-level credentials appropriate to each integration surface.
Ship the agent experience. Let the runtime carry the operational weight.
We are working with technical teams building agents that must operate across real systems.