Skip to main content
Resolve the delivery behavior for one recipient, optional Persona, and optional tag. The Directory reads one finalized chain snapshot, selects the authoritative document or frozen legacy generation for each scope, and interprets supported rules locally. The chain validates publication authority and integrity; it does not interpret document actions. The response provides the decision used for original client messages and ordinary DID-service fall-through. One applied decision remains fixed for that delivery attempt. Compatible clients can also call this endpoint to identify limits before submitting a large encrypted payload.

Request

string
required
Canonical recipient DID. Resolve an alias before calling this endpoint.
string
Persona parsed from the optional @persona target suffix.
string
Exact public top-level envelope tag. Tags are case-sensitive.

Winning policy response

200 Response
source is persona or did when a rule wins. The action is the resolved execution representation, which can use a DeliveryPlan/v1 even when the published document uses a direct action. For a document-backed winner, the response also includes policy_document with its exact bytes, revision, owner, hash, cleared state, and finalized block context, plus policy_base_constraints. Keep that generation context with the decision. An explicit cleared document suppresses frozen policies for that scope. Only absence of a document record permits frozen V3/V2 reads. Unsupported or invalid document bytes cause resolution to fail; they never enable legacy fallback.

Fall-through response

A valid recipient with no matching rule still returns 200:
200 Response
applied: false instructs a Relay to use ordinary DID services. It is not equivalent to a failed lookup. Fall-through does not discard scope limits. effective_constraints remains the network-clamped minimum of the recipient DID constraints and, when addressed, the active Persona constraints. max_message_bytes and max_chunks are deprecated Policy V2 compatibility fields. Their sentinel values mean the resolver does not impose an aggregate-size or group-cardinality limit.

Errors

Do not treat 409 or 502 as a policy-free result. The legacy POST /delivery-policies/resolve path cannot resolve scopes with document records; use the version-aware route above.

Straight to the point

  • Authentication: none
  • Selection: Persona rule, then DID rule, then no-policy fall-through
  • State: finalized block identified in the response
  • No matching policy: 200 with applied: false