DemoPricing
NewAuthorize the act, not the agent →
Computable authority · For institutions

Authority your agents carry to institutions they have never met.

Your agent presents signed authority to a bank, supplier or counterparty. Their system verifies it offline against your public key before acting. Yours independently verifies the authority presented by theirs. No prior integration. No call to NOMOS. No model in the decision.

In private pilot with leading financial and government institutions. Early access available.
system of record · lending1 / 5

loading the verifier…

·Envelope
·Audience
·Window
·Nonce
·Issuer, seal and currency
·Testimony
·Fact sources and types
·Evaluation
·Consents
The open verifier and the published SPEC-008 test vectors, running here. Nothing is sent anywhere.Why the agent is not an input ↗
Triangulation · how the authority is built

Verify every AI decision against how your organisation actually works.

NOMOS reconciles policy, behavior and outcomes into a sealed, machine-executable authority artifact, then verifies every decision against it before it runs.

One API call. Authorized, denied or escalated. Full audit trail.
first seal free
Find where policy and reality divergeUpload your policy, your decision logs and what happened afterwards. NOMOS checks every rule against every decision, finds where practice departs, and measures whether that made outcomes better or worse.
Gap analysisEXAMPLElending.nomos
DE JURE — POLICYDE FACTO — REALITYOUTCOME & ACTION
Escalate loans > $10kTeam escalates > $25k
No clear effectYour call: enforce $10k or write in $25k328 decisions · defaults no different
Verify ID on all accountsSkipped on most under $300
Harmful driftEnforce ID checks below $300270 decisions · +4.1 pts fraud
Manager approval requiredAuto-approved on weekends
Harmful driftRemove weekend auto-approval404 decisions · +8.1 pts charge-offs
3 departures from policy2 harmful1 no clear effectCodify what outcomes support, enforce what they don't, and see where the data can't tell yet.
Learn more:···

Written policy is a claim. Behavior is evidence. Outcomes are proof. NOMOS reconciles all three and seals the result as something your systems can call.

FIG 0.1
Extracted, not authored
Conditions, thresholds and escalation rules pulled straight from your SOPs and credit policies.
FIG 0.2
Behavior, at population scale
Every real decision compared against the rule that was supposed to decide it.
FIG 0.3
Sealed, then enforced
A cryptographically sealed artifact your systems call before acting. Immutable and versioned.

Seal the authority

Your policy, reconciled with how your teams actually decide, becomes sealed, versioned rules: conditions, outcomes, priorities, a default, escalations and a data contract. Your key signs it. Start from a template or fork one in Studio against your own documents.

2.0
Artifact registry
kyc.nomosKYC Customer Verification12 rules
fraud.nomosTransaction Fraud Detection13 rules
refunds.nomosCustomer Refund Policy10 rules
hr-leave.nomosHR Leave Approval10 rules
lending.nomosTEMPLATE
Consumer Loan Approval
12 rules covering credit floors, DTI, employment type, delinquency history and dual-approval tiers.
signed byyour issuer key
version1.0
audit_trailimmutable
Learn more:···
Authorize the act, not the agent

The agent is not an input to the verdict.

An honest agent that was misled looks exactly like a compromised one. So authority travels inside the act, and the system the action would change checks it. An agent that holds no authority cannot be a confused deputy.

V = EvalA(a, F, t)
Athe institution's sealed authorityathe exact actionFthe proven factstthe moment of action

No term for who asks. The verdict is AUTHORIZED, DENIED, ESCALATED or INCOMPLETE.

Nor does the agent choose which law applies. The system that would change works out every authority that governs the action, from registrars it pins, and commits only when each one allows it. Part III ↗

02 · carry
The agent carries an Act

The exact action, the sealed authority, testimony from certified witnesses, approvals bound to this exact act, an audience, a nonce and a short window. The agent holds no key that matters.

03 · verify
The system of record decides

Nine checks, stopping at the first failure. Facts come from witnesses or its own records, never from the agent. A missing fact is undecided, never false.

04 · commit
Exactly this change, once

On AUTHORIZED it applies exactly the action, records the nonce and re-reads its own facts in one step. Anything else commits nothing.

Enforce it in one API call

Point your agent at the authority. Every decision returns authorized, denied or escalated, with the rule that decided it and a hash you can hand to an auditor.

3.0
nomosPROD
Decision queue12
Artifacts7
Gap analysis
Audit log
SEALED
lending.nomos
kyc.nomos
fraud.nomos
refunds.nomos
Decision queueEXAMPLE
VERDICTDECISIONAMOUNTRULEMS
AUTHORIZEDapprove_loan · 8821$14,200auto_appr62
AUTHORIZEDapprove_loan · 8822$3,400auto_appr48
ESCALATEDapprove_loan · 8823$31,900threshold71
AUTHORIZEDapprove_loan · 8824$9,150auto_appr55
DENIEDverify_id · 8825$620id_check44
AUTHORIZEDapprove_loan · 8826$2,780auto_appr51
AUTHORIZEDrefund_req · 8827$142return_win39
AUTHORIZEDapprove_loan · 8828$7,300auto_appr58
→ every verdict sealed againstlending.nomos
nomos.can()AUTHORIZED
import { nomos } from '@nomosprotocol/sdk';
const verdict = await nomos.can({
authority: 'pub_lending_v1',
amount: 15000,
credit_score: 720,
income_to_repayment_ratio: 3.2,
});
// verdict.allowed → true
// verdict.verdict → "AUTHORIZED"
// verdict.url → "/queries/qry_8f2a1c…"

No API key, no signup — nomos.can() queries any published Exchange authority directly and hands back a verdict with a permanent, independently verifiable transcript URL.

Learn more:···

Watch the gap reopen

Reality keeps moving. NOMOS tracks outcomes after every verified decision and flags when behavior starts drifting from the sealed artifact again — before it becomes an audit finding.

4.0
Outcome trackingEXAMPLE
Drift detected14 days
Weekend auto-approvals resumed on lending.nomos despite the sealed rule.
flagged268 decisions
charge_offs+5.1%
confidencecausal · p<0.01
Learn more:···
Open-source offline verifier@nomosprotocol/verify ↗
No model in the decisiondeterministic
Regulators co-sign without re-sealingSPEC-004 ↗
Revocations published and checkedSPEC-006 ↗
Authority carried between strangersSPEC-007 · 008 ↗
Your own keys in AWS, Google Cloud or AzureRegulated plan
A paradigm shift

From the agent to the act.

Agent security starts with permissions: who the agent is, and what it may do. But when injected text misleads an agent, its identity, credentials and operator stay the same. An honest agent misled by injected text and a compromised agent are indistinguishable at the moment they act. So authority has to attach to the action, not the agent.

The old question
What is this agent allowed to do?
The new question
Is this action authorized, on these facts, right now?
Swipe to compare →
NOMOS
THE ACT
Harnesses
THE AGENT
Guardrails
THE MODEL
Policy-as-code
THE REQUEST
Process mining
THE RECORD
The question it answers
Is this action authorized, on these facts, right now?
What may this agent try?
What may this model say?
Does this request pass our rules?
What already happened?
Who runs the check
The system being changed
Whoever runs the agent
Whoever runs the model or app
The service owner
A platform reading event logs
If the agent is misled or compromised
The system being changed still checks the action
Only as strong as checks in the agent's own path
May catch the injected text
Still enforced, if it runs on the service
Seen afterwards, if logged
If the agent states its own facts
Refused, unless the rules accept that source
Accepted unless a hook or check rejects it
Can flag them as unsupported, not prove them
Used as given, unless the policy looks them up
Visible only if logged
If the action changes after approval
Refused
Depends on the setup
Not designed for this
Only if you build it
Can be flagged, if logged
Proof afterwards
A receipt, plus the exact Act to re-verify
The operator's own logs and traces
Logs
Decision logs with the input and policy
Event logs
Where it sits

Permissions decide what an agent may do.

NOMOS decides what is allowed to change.

Before anything commits, the system being changed checks the action against your institution's signed rules. If it doesn't pass, nothing changes.

Start with one call: nomos.can() checks an action against signed rules. You state the facts, and it answers. Add an Act when the answer has to bind. Read the paper ↗

Where institutions start

One high-stakes decision, usually the one an auditor or a regulator already asked about. Then the next, on the same authority.

BANKS · LENDING
Consumer loans
An agent approves loans inside the credit policy. Above the limit it waits for two senior approvers; a missing bureau fact commits nothing.
BANKS · ONBOARDING
KYC and AML
Accounts open only when sanctions screening and ID checks are testified by the systems that ran them, never asserted by the agent.
PAYMENTS
Fraud and payouts
Payments released within limits. Lost cards, velocity and blocked jurisdictions are refused before money moves.
INSURERS
Claims
Claims settle within delegated authority. Anything larger escalates to a named handler, bound to that exact claim and amount.
REGULATORS · CENTRAL BANKS
Supervisory rules
Publish rules every supervised system checks itself against, and co-sign an institution's policy without re-sealing it.
GOVERNMENT
Public services
Eligibility, permits and benefits decided the same way by every agency system and agent, and checkable by anyone, offline.
EDUCATION AUTHORITIES
Policy distribution
An authority issues policy once. Every school runs the version in force and acknowledges each update.
ENTERPRISE OPERATIONS
Everyday approvals
Refunds, leave and purchasing, each with its limits and the people who must approve above them.
WHO USES IT
Risk and compliance teams
Banks, insurers, payments
Regulators and supervisors
Central banks and authorities
Government digital teams
Ministries and agencies
Platform and AI teams
The systems that act

Pricing

Seal your first artifact free. Pay when you put it in production.

FREE
$0/month
Seal your first authority artifact, free.
1 custom sealed artifact
Unlimited public template forks
1,000 verifications / month
Contradiction detection
API key — your artifact + all public templates
PRODUCTIONPOPULAR
$299/month
Run your authority in production.
Unlimited authority artifacts
100K verifications / month
$0.01 per additional verification
Behavioral triangulation
Outcome tracking + drift detection
Simulation back-testing
Decision queue (human review)
5 team members · priority support
Full API access
REGULATED
Custom
For banks, insurers and public bodies under formal supervision.
Everything in Production
Unlimited verifications
Single sign-on and webhooks
Audit and registry exports
SLA guarantees
Dedicated support

Questions worth asking

Straight answers about how NOMOS works, what it stores, and what it doesn't claim to do.

THE SHIFT

Identity and permissions tell a system who is calling and what it may generally do, not whether to do what it asks now. When injected text misleads an agent, its identity, credentials and operator stay the same, so nothing looks wrong. NOMOS checks the action itself: the system being changed verifies it against the institution's signed rules and the facts they require, before anything commits.

No, keep them. They help an agent work reliably and show who is calling. But a check in the agent's own path can't have the final word, because the agent controls its own path. NOMOS adds the check on the system being changed.

Not for the verdict. Think of a border: a traveller can present any documents they like, but entry is granted only at the point that checks them. The agent chooses which action to propose, and the verdict doesn't depend on who carries it. Whatever the agent adds or leaves out, the action commits only if the authority permits it on the required facts, or the right people approved it. This holds when the system accepts the change only through a verified Act.

IF YOU RUN A HARNESS

A harness is everything around the model that helps it do real work: tools, memory, permissions, tests and traces. Whoever runs the agent runs the harness. NOMOS works on the other side of the action: the system being changed checks whether this action is authorized before it commits.

Keep your harness. If you own both the agent and the system, the risk is low and nobody outside needs proof, it may be enough. NOMOS matters when agents you don't control reach your systems, when a misled agent could make a costly change, or when an auditor or counterparty has to verify the decision.

No. Those run on the agent's side and are recorded by whoever runs the agent. They can't bind a system that belongs to someone else, and if the harness is misconfigured or compromised, its checks may not run. With an Act, the system being changed verifies the action itself, and an auditor can re-verify the exact Act later.

A check inside the agent's own process is advice, not enforcement: if the agent holds an API key to the system, or can run code where the check runs, it has a path around it. A gateway can enforce only if it holds the only credential able to make the change. It then takes on the full job of the system being changed, including checking where each fact came from, tying approvals to the exact action, and committing each action only once.

Yes. Your agent can carry Acts with act() or through the act tool on the NOMOS MCP server, and your harness can call nomos.can() as one of its checks. nomos.can() answers on the facts you state; only an Act binds the system being changed.

HOW IT DECIDES

No. Models help extract rules from your documents, and people review them. The verdict is computed deterministically from the sealed authority: the same action, facts and time always give the same verdict.

A fact the authority says must come from a witness is refused if the agent supplies it. A missing fact is undecided, never false: if it could change the outcome, the verdict is INCOMPLETE, nothing is committed, and the missing fact is named.

The authority can require named roles to approve. Each approval is signed over this exact act, so it cannot be reused for a changed amount or a different action, and two keys belonging to one person count once.

You seal a new version. An older version can no longer authorize a new action, but it still verifies the decisions made while it was in force.

TRUST

Yes. Authorities and approvals are signed (Ed25519 or ES256). Anyone verifies them with the issuer's public key and the open-source verifier, offline.

Yes. The system the action would change verifies the Act itself. The network brings one thing: news of a revocation.

By default NOMOS seals with its platform key. On the Regulated plan you seal with your own keys in AWS KMS, Google Cloud KMS, Azure Key Vault or an HSM, and approvers can sign with passkeys.

The issuer publishes a signed revocation. A verifier that checks it refuses the authority from then on.

GETTING STARTED

A policy document: PDF, Word or plain text. Add a CSV of past decisions to see where practice departs from the written rules.

nomos.can() for a verdict, act() to carry an Act, accept() to be the system that commits it. A TypeScript SDK, a REST API and an MCP server.

No, and we won't claim it. NOMOS produces the decision-level evidence a compliance programme needs. Certification is your auditor's call, not ours.

NOMOS runs in a single region today. Verification itself can run entirely inside your environment with the open-source verifier.

Changelog

The specs ↗
Nov 12, 2026
Which laws apply

accept() works out every authority that governs an action, from registrars you pin, and commits only when the Act carries each one.

Nov 3, 2026
Enterprise single sign-on

OIDC and SAML 2.0, verified domains, and require-SSO with an owner break-glass.

Nov 3, 2026
Institution keys in your own KMS

Seal and sign with keys held in AWS KMS, Google Cloud KMS, Azure Key Vault or your HSM.

Oct 27, 2026
Passkey approvals

An approver signs with a passkey bound to the exact Act. A touch alone is not an approval.

Authority any system can check.

In private pilot with leading financial and government institutions. Early access available.