Integrations

Connect your agents

The early MVP ships three integration paths. All routes flow through the same decision pipeline: POST /v1/intercept/tool-call.

Pi guarded adapter

Wrap Pi file and shell tools. Every call is intercepted before execution.

import { guardedRead, guardedBash } from "@actantos/pi-adapter";

await guardedRead("README.md");          // allow
await guardedRead(".env");               // deny
await guardedBash("git push origin main"); // approval_required

MCP policy gateway

Configure MCP clients (Cursor, Claude Desktop, custom SDKs) to connect to ActantOS instead of upstream MCP servers directly. The gateway pins tool manifests, blocks SSRF targets, and intercepts tools/call.

See the architecture overview for the trust-boundary diagram.

HTTP decision API

Any agent runtime can integrate by posting normalized tool calls to actantosd. Custom adapters must fail closed on timeout or daemon unavailability.

API reference →