DelegusDocsv0.3 rc1

Docs

Documentation

Delegus documentation

These docs are for services that get requests from AI agents they’ve never dealt with. They show how to check an agent’s claimed authority before you act on it, and how to keep the signed answer. We wrote the protocol down first, and the service and the SDK are built from it.

Quickstart: your first signed decision

Sign up, copy your verify key, send one request and keep the signed receipt. The sandbox is free, with no card.

Start the quickstart →

How the pieces fit

PartyDoesWhere it is specified
PrincipalA company. Proves control of its domain, signs Grants for its agents, revokes them.§2.1, §3, §7
AgentHolds a key. Signs a Proof for each request, bound to the Grant, the recipient and the action.§2.2, §4
Relying partyYour service. Forwards Grant, Proof and action to Delegus in one call and keeps the receipt.§2.3, §5, Integrate
DelegusEvaluates the profile's checks in fixed order, fails closed, signs the receipt, preserves the evidence.§5, §6, §8

Reference

The v0.2 protocol documents are frozen, as they stood before v0.3 went live, under /docs/v0.2/: the specification, its Markdown, the profile delegus-base-v1, the reason codes and the errata. Other /docs/v0.2/ paths show the current page. The unversioned paths follow the current version.

Documents

Status

The protocol engine @delegus/core and the SDK @delegus/sdk are Apache-2.0; anyone can run the open checks. The Delegus service, which signs decisions and preserves evidence, is not open source. v0.3 (release candidate 1) is the current specification, and new relying parties start on it; v0.2 is frozen and stays the normative text until v0.3 is frozen. The production API is serving at api.delegus.ai, with self-serve signup at app.delegus.ai; @delegus/core, @delegus/sdk, @delegus/conformance and the MCP gateway @delegus/mcp-gateway are on npm, and the Python MCP middleware delegus-mcp is on PyPI. Nothing here is a measured figure or a guarantee.