Decision playground

Pick a request, get the decision and its signed receipt, and verify the signature in your browser. Then change one field of the receipt and watch verification fail.

Choose a preset and press Decide.

receipt.json

JavaScript is off

The playground runs in your browser. The recorded responses it uses in REPLAY mode are at replay.json, and every quickstart does the same verification from a terminal.

Evidence grade of every playground receipt

Evidence grade Rung 2 · Operational

Covers

Which rule decided this request and that the record was not changed after signing. Not whether the sender was an AI agent.

Confidence

None stated. No calibrated confidence applies to this record.

Calibration

Uncalibrated

Known error rates

None measured. Silvector publishes no detection error rate yet.

Basis

The deterministic decide() rule shown above
Ed25519 signature over the canonical receipt body, checked against the published JWKS

Bias risks

The decision is only as good as the facts it was given. A request with no signature claim is not_identified, which is not a finding that a person or an agent sent it.

Next step

To ask who was behind a series of requests, keep the receipts and escalate to rung 3 with at least two independent signal families. How escalation works

Assigned by

These docs, from the rung definitions. The grade is not a signed field of the receipt.

Reading the result

allow lets the request through. step up asks for more, such as a fresh factor. deny is only for requests that fail a verified check.
The identity verdict says what was verified about the sender's claim. not_identified means no claim was made; it says nothing either way about whether a person or an agent sent it.
A User-Agent that claims to be a known crawler is checked against that operator's published network ranges. A claim from outside them is verification_failed.
A "signature": "valid" field in a JSON body is ignored, and the response says so. Only a real HTTP message signature can verify an agent.

How it works

Live mode sends your request shape to POST /v1/check through this site's own origin, which forwards only the public check, key set and health routes. Verification happens in your browser with Web Crypto against GET /.well-known/jwks.json. Replay mode uses real responses recorded from the live API, verified against the key set recorded with them.

If the live API is unreachable or rate limited (60 requests a minute per caller), the playground falls back to the recorded responses and labels them REPLAY.