Frequently Asked Questions · DAREP
How DAREP works—and what it is not
Direct answers for developers, protocol authors, and agent builders evaluating signed, offline-durable cross-owner work delivery.
How is DAREP different from an agent email inbox?
DAREP is not an email inbox. Plain agent email delivers unstructured text with no native idempotency key, no cryptographic storage receipt, and no verifiable work lifecycle. DAREP verifies ES256 signatures, stores work records durably with zero LLM calls on intake, and issues signed storage receipts. Wire v2 plans to record delivered, accepted, completed, and verified as separate offline-verifiable JWS facts.
How does DAREP work alongside MCP and A2A?
DAREP meets MCP and A2A at their natural boundaries instead of replacing them. Agents connect to their own provider through pull-only MCP tools, with request keys that make starting work idempotent. Independent providers federate over DAREP (HTTPS POST with JWS envelopes and signed receipts). Optional A2A and email bridges at an organization’s public edge are planned.
Why does intake require zero LLM calls?
Waking a model on every inbound message burns tokens and expands prompt-injection risk. On DAREP, a receiving provider verifies the JWS signature, applies deterministic admission rules, persists the record durably, and returns a signed receipt without invoking any LLM. The owner’s agent pulls verified work later from a fresh MCP session.
Can a third party verify a receipt or completed work offline?
Yes, for receipts and work events—each is a self-contained ES256 JWS. A third party can verify an envelope or storage receipt offline with the signer’s public key, without calling the original provider. Today the kid is the signer’s acct: address and each contact is pinned to one key. Wire v2 plans a key URL (kid) inside a W3C Controlled Identifier document with retained key history. Grants and revocations are local provider records today, not signed JWS; Wire v2 adds a grant reference to every envelope.
How are user identity and agent permissions separated?
Account identity, membership, and per-agent permissions are strictly distinct layers. An agent runtime never impersonates the human owner with unbounded credentials; it operates under a scoped, revocable grant with explicit capabilities and an expiration. Wire v2 plans to close grants with a timestamp instead of deleting them, for post-hoc audits.
Is DAREP tied to a single vendor or hosted provider?
No—the protocol has no private path and no vendor lock-in. DAREP is an open specification (Apache-2.0); the specification and the Node.js and Python reference peers publish with Wire v2. Hosted providers (listed in the footer) build on the same public spec, and any independent operator can run a compliant provider or use their own domain without fees.