# Golem

> AI Detection and Response (AiDR) for agents. Golem sits in the path of every tool call: it detects hijacked or drifting agents, blocks or gates the dangerous calls before they execute, contains a compromised machine, and signs the evidence so the record cannot be edited afterward. Free public preview.

Golem is AI Detection and Response for AI agents, the agent-layer counterpart to EDR for endpoints and NDR for networks. It has all three parts of that category:

- **Sensor (in-path).** Golem is the layer an agent's tool calls travel through: Model Context Protocol (MCP), agent hooks, SDKs and provider APIs. It is not a reader of log files after the fact. Being in the path is what makes blocking possible.
- **Detection (fast in the path, deep behind it).** The block decision is made in-process from a pre-compiled, cost-bounded CEL rule. No network hop, no model, no second round trip, nothing the agent waits on. Judgment happens behind the call, where a reviewer model reads what an agent said beside what it did, because misalignment is a property of that sequence. Enforcement runs at the speed of the call. Deep analysis runs only on the sessions that earn it. Reading payload bodies is its own opt-in switch, off by default.
- **Response.** Block the call at the wire, hold it for human approval, or clamp a whole host to a locked-down toolset from the server. Containment is reversible by design. No detector is accurate enough to justify an irreversible action.

Every action is hashed and signed as it passes (COSE_Sign1 over a canonical CBOR bill of materials), the raw payload goes to customer-controlled storage, and the hash goes to an append-only transparency log. That is what separates Golem from the rest of the category. Elsewhere a detection or a block is a claim in a log the host wrote. Here it is a signed entry the actor cannot rewrite.

Golem exposes two capabilities to agents over MCP, discoverable via the Agentic Resource Discovery (ARD) catalog and authorized through standard OAuth (scoped, short-lived, revocable tokens):

- Golem Context: search an agent's own conversation history, recall durable context, and pull artifacts from the tamper-evident ledger.
- Golem Safety: an action-time verdict on whether a URL or tool target is safe to connect to, from aggregated threat intelligence.

## Agent discovery and onboarding

- [ARD capability catalog](https://golem.team/.well-known/ai-catalog.json): Machine-readable catalog of Golem's MCP capabilities.
- [Agent registration guide (auth.md)](https://app.golem.team/auth.md): How an agent registers and obtains a scoped token: Agent-Verified (headless), User-Claimed (device flow), and keyless Instant Trial.
- [OAuth authorization metadata](https://app.golem.team/.well-known/oauth-authorization-server): RFC 8414 metadata for token, registration and device-authorization endpoints, plus supported scopes.
- [App-hosted ARD catalog](https://app.golem.team/.well-known/ai-catalog.json): The live catalog served by the Golem control plane.

## Main pages

- [Golem home](https://golem.team): What Golem does, how it works, and how to start the free public preview.