CasimirBot / Helix

Agent Access

Connection information for the provider-neutral CasimirBot external-agent harness.

An explicit connection is required

A model that retrieves this public page can read and cite it, but retrieval alone cannot invoke CasimirBot tools. A user, application developer, plugin, or surrounding agent harness must configure the MCP endpoint and authorize access.

Credentials belong in the client's OAuth connection. Do not put access tokens or secrets in prompts or URLs.

Service endpoints

SurfaceCanonical URLPurpose
MCPhttps://casimirbot.com/mcpOAuth-protected, stateless Streamable HTTP MCP requests.
Durable-run REST APIhttps://casimirbot.com/api/v1/agent-runsOAuth-protected durable run lifecycle.
Shared Live Room REST APIhttps://casimirbot.com/api/v1/roomsOAuth-protected room, run-binding, and deferred source control.
OAuth metadatahttps://casimirbot.com/.well-known/oauth-protected-resource/mcpProtected-resource discovery for authorization clients.
API contracthttps://casimirbot.com/docs/architecture/helix-agent-api-v1.mdRun lifecycle, schemas, scopes, and safety boundaries.
Workstationhttps://casimirbot.com/open?panels=agent-access&focus=agent-access&entry=workstationHuman-facing connection and configuration surface.
CasimirBot metadatahttps://casimirbot.com/agent-access.jsonMachine-readable links from this page; not a standards-defined manifest.

Core durable-run MCP tools

These are the stable run-lifecycle tools. The authenticated MCP tools/list response is the source of truth for the complete catalog, including Shared Live Room tools. Each tool declares its complete required OAuth scope set, which is enforced when called.

Durable run model

Clients start a bounded run, retain its opaque run_id, and continue or inspect that same run. Results include structured status, evidence references, unresolved requirements, and recommended next actions.