Register an autonomous filing agent
Use this service to apply for recognition of a specific software agent that will file on behalf of your clients. Your firm must already be registered with HMRC and supervised for anti-money-laundering.
Firm and accountability
The agent
Requested authority
Expressed as RFC 9396 authorization_details. Limits are ceilings the authority may lower; the running totals are held by the authority, not the agent.
Application submitted
Your reference
A case officer will run automated checks against the registers and make a decision. Switch to the to continue.
Application —
No application in the queue. Submit one from the .
Automated checks
Each check is a plain rule evaluated against a named source. The engine drafts; it does not decide.
| Rule | Check | Source | Result |
|---|
Decision
All automated checks passed. The decision is yours and will be recorded against your name.
Passport issued
Decoded credential (JWT, EdDSA / Ed25519)
Header
Payload
Compact token
Signature verified in this browser against the authority's public key using WebCrypto Ed25519. The token carries the limits; the running totals and the revocation status live in the authority's registry, never in the token.
Supervisory actions
- No actions recorded.
Verification console
Each button is a proposed action by the agent. The gateway runs the ordered checks (signature, status, authorisation, scope, limits, escalation) and returns a verdict with its rule.
Proposed actions
- Waiting for a proposed action.
Ordered rule evaluation (deny by default)
What this prototype shows
An AI agent can be correctly identified and still act beyond what its principal allowed. Identity is not authority. The Agent Passport is the authority's own record of what a specific agent may do, checked at the moment it tries to do it.
The demo in seven beats
- The firm submits a pre-filled application (Operator).
- Seven automated checks pass, each citing a rule and a source (Regulator).
- A named officer approves; an Ed25519-signed credential is minted in the browser and verified against the public key.
- The console allows a £1,400 VAT return, escalates a £4,200 quarterly update, denies a client not on the 64-8 list, denies a £9,400 filing over the per-filing cap.
- Repeated allowed filings breach the £20,000 rolling cap: structuring caught by state the token cannot hold.
- The officer revokes. The next action is denied on status, before any other rule runs.
- Every line of the log is hash-chained to the previous one and names the rule-pack version. Not a blockchain: a tamper-evident file.
What is real here, and what is not
- Real: the signature (WebCrypto Ed25519), the ordered deterministic rules, the stateful cumulative counter, revocation via registry lookup, the SHA-256 audit chain.
- Not real: the registers (synthetic), HMRC involvement (none), persistence (page state only), holder binding (
cnfleft null; Rung 2), sanctions screening.
Standards used
JWT (RFC 7519) · EdDSA / Ed25519 (RFC 8037) · authorization_details (RFC 9396) · cnf reserved for DPoP binding (RFC 7800 / 9449) · registry status lookup in the shape of a status list.
Lexis Labs · C:\>DIR Global 'Agentic Regulator' Hackathon · Know Your Agent problem space · synthetic data only.