NOMOS status
Answered our latest tool-list check 15 hours ago with 7 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 18:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 18:17 | Answered | 3.5 s | 7 |
Tools (7)
Read from the server on 16 Nov 2026.
- verify_decision
- Check whether an AI decision is allowed, denied, or needs escalation according to a sealed NOMOS governance artifact. Always returns `allowed` (boolean) — that field is safe to read regardless of which artifact type answered. The rest of the shape genuinely differs by artifact type, because it proxies two different underlying endpoints: pub_ demo artifacts return a flat shape (`outcome`: auto_appr
- generate_governance
- Convert one or more policy documents into a sealed NOMOS governance artifact (.nomos). Extracts executable rules using Claude, detects contradictions between rules, computes an Autonomy Readiness Index (ARI) score (0–1), and cryptographically seals the result. Returns an artifact_id you can use with verify_decision immediately. Optionally accepts historical behavioral decision logs to add a behavi
- detect_contradictions
- Analyze policy documents (and optional behavioral decision logs) to detect contradictions, hidden rules, and gaps between declared policy and observed behavior. Stateless — no artifact is created and nothing is persisted. Returns contradictions of three types: rule_collision (two rules that apply to the same case with different decisions where the policy does not settle it soundly, each with that
- ask_authority
- Query a published authority on the NOMOS Exchange marketplace — a different system from verify_decision's own sealed policies. Every public authority (e.g. eu-ai-act.nomos) is queryable with no key. Returns the authority's own verdict (AUTHORIZED/DENIED/ESCALATED), the exact rule and reason, and a permanent, cryptographically-bound transcript (query_id + url) — replayable evidence, not just a repl
- ask_by_context
- Ask whether an action is allowed WITHOUT choosing the law yourself (NOMOS-SPEC-014). Describe where the act happens and who it involves; NOMOS works out from its signed registrar log which laws govern it, asks every one, and combines strictly: any deny denies, a yes needs every law. Prefer this over ask_authority whenever you do not already know which law applies: naming one law leaves out the oth
- find_authority
- Find which published authorities on the NOMOS Exchange govern something you are about to do, from a plain description (e.g. "deploy a recruitment model in the EU"). No name needed. Returns the matching authorities ranked, and for each the facts it reads that match your description (what to pass to ask_authority as inputs) and its most relevant rules with where they come from in the source. Also re
- request_authority
- Ask for an authority (a law, regulation, standard or policy) to be added to the NOMOS Exchange when find_authority finds nothing. Requests are public and ranked by how many asked; they decide what is compiled next. Repeated requests from one caller count once. This never creates an authority: only its issuer, or NOMOS compiling the public text, can.