Delegus

Is this agent allowed to do this, for this company, right now?

Software is starting to receive actions from AI agents it has never met. Delegus answers that question in one API call, and signs the answer, so the decision holds up later.

See the integration

One call. Two outcomes. Nothing to learn first.

The agent presents two headers with its request: a grant signed by the company it works for, and a proof signed with its own key. The receiving service forwards both, plus what it actually received, to Delegus.

// The relying party's entire integration
import { Delegus } from "@delegus/sdk";
const delegus = new Delegus({ apiKey: process.env.DELEGUS_API_KEY });

app.post("/orders", async (req, res) => {
  const d = await delegus.verify({
    grant:  req.header("Delegus-Grant"),
    proof:  req.header("Delegus-Proof"),
    action: { type: "commerce:purchase", resource: req.body.orderId,
              amount: req.body.amountMinor, currency: req.body.currency },
  });
  if (d.decision !== "ALLOW") return res.status(403).json({ reason: d.reason });
  // proceed, and keep d.receipt with the order
});

No DIDs, credentials, or status lists to understand. If a denial comes back, it says why: AMOUNT_EXCEEDS_AUTHORITY, AUTHORITY_REVOKED, PROOF_REPLAYED, and so on. The engineer who has never seen the agent before can ship this in an afternoon.

How authority travels from a company to a stranger's server

Every link is a signature or a domain proof. The only party asserting anything on its own authority is Delegus, at the end, and it signs what it asserted.

  1. acme.comAcme proves it controls its domain. Delegus re-checks every day.
  2. Acme signs a grant“Our purchasing agent may buy, up to $500, until October 1.” Scoped, time-boxed, revocable.
  3. The agent signs each requestA proof bound to this grant, this recipient, this exact action, this moment. It cannot be replayed or forwarded.
  4. The seller calls DelegusForwards the grant, the proof, and the action it received.
  5. Delegus decides and signsSignatures, validity, revocation, binding, freshness, scope. Then one word, and a receipt.

Acme can revoke the grant at any moment. The next verification anywhere in the world denies. There is no propagation window.

Every decision leaves evidence that outlives it

The receipt pins hashes of the grant, the request, the company's key document as it stood, the revocation list as it stood, the exact rules applied, and the evaluation time. Delegus signs the whole thing and keeps the referenced artifacts.

Two years later, anyone with the receipt can re-run the open protocol checks against those preserved snapshots and get the same result. If a partner ever asks who let that happen, the answer is a signed document, not a log search.

Outcomes are recorded too. The receiving service reports what happened afterward — fulfilled, disputed, resolved — and nothing is ever overwritten. Over time that turns decisions into something rarer than identity data: a record of authority, decision, reliance, and outcome.

Open format. Closed service.

Anyone can verify a Delegus artifact without calling Delegus. Nobody else can produce a fresh one.

Published and reproducible

  • Grant semantics and the constraint vocabulary
  • Proof format, bound to the HTTP request
  • Protocol verification rules, versioned and hashed
  • Receipt and outcome formats
  • Portable identity: bring your own did:web

Run by Delegus

  • Issuer trust and domain verification
  • Live revocation and replay protection
  • Decision signing and evidence preservation
  • Adapters for the identity systems agents already have
  • The outcome graph, and what it eventually makes possible

Starting where agents already spend money on behalf of companies

Business procurement is going autonomous first. Company A's agent buys GPU hours, dataset access, or software seats from Company B's API. The money can move; what's missing is a way for B to know that A's agent was authorized to spend it.

$15 trillion

of B2B purchases are projected to be intermediated by AI agents by 2028, per Gartner. Payment networks answer whether the money can move. Delegus answers the prior question: was this machine authorized by this company to enter this transaction?

We're onboarding ten design partners

Five companies running procurement agents, five selling machine-provisionable resources through an API. You get the integration, the receipts, and a direct line to the people writing the protocol. We get real traffic and honest feedback.

Talk to us about a pilot