Check a candidate deployment-wide declaration without persisting anything

Answers whether a candidate declaration would be admitted, and reports the rules it
would be admitted under. Writes nothing, reads nothing from the registry, and
contacts nothing over the network.

The candidate goes through the identical admission expression the real

declare runs, on a candidate built with the same DEPLOYMENT scope. That identity is
the point: a dry run that checked less than the real path is the recorded defect
where a configuration-time self-test passed green and the runtime failed at the
moment that mattered. A green verdict here means the declaration will succeed.

The reported derivedAudience is therefore the deployment

audience — the value a workload bound through this issuer will actually have to
present — and not a tenant-shaped one.

A refused candidate is still a 200. The verdict is the answer to the

question that was asked, not an error; the refusal reason travels in the body.
Whether the issuer can be REACHED is the separate test verb, which is
the one that opens a socket.

Never entitlement-gated. No Edition widens or narrows this plane. These are

the deployment operator's own declarations rather than a tenant's, so there is no
Edition to consult (FR-181.16).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

The candidate declaration, in exactly the shape declare accepts.

A trusted-issuer declaration. Carries no credential of any kind: ANKASecure verifies tokens from this issuer against the PUBLIC key set the issuer publishes, so there is no secret to submit, store, seal or rotate.

string
enum
required

The vendor mechanism. It NARROWS the platform algorithm allow-list and can never widen it; choose GENERIC_OIDC for any provider not named here.

Allowed:
string
required
length between 0 and 2048

The issuer identifier, exactly as the provider publishes it in its OpenID Connect discovery document. HTTPS only, no query and no fragment (OpenID Connect Discovery 1.0 section 2). It is stored in canonical form — lowercase scheme and host, the default port removed, no trailing slash — because that string is both the uniqueness key and the value a presented token's iss claim is compared against.

string
length between 0 and 200

An operator-chosen label. Carries no meaning to any rule and is never compared against anything in a token.

permittedAlgorithms
array of strings
length between 0 and 9

The signature algorithms a token from this issuer may use. Omit it to accept the preset's own set. Every entry must be a member of that set — a narrower list is admitted, a wider one is refused by name.

permittedAlgorithms
string
required

The longest exp - iat a token from this issuer may declare, as an ISO-8601 duration. It may LOWER the platform ceiling and never raise it. The ceiling is an accept-or-refuse gate on the ISSUER rather than a bound on any one token: a declaration above it is refused outright, and every token that issuer mints is refused with it, a five-minute one included.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json