Operational - Early Preview Whitepaper v0.15, 27 October 2026 Platform release 0.36 / schema v0.4 / floor v0.5
Use the API

One question before every action

An AI agent describes what it is about to do. The API checks it against the guardrails that apply and answers with a signed verdict and the reasons: go ahead, go ahead with conditions, ask a person, or stop. You can call it from code, plug it into an agent framework, enforce it at a gateway, or use it with no code at all.

Who uses it

Five ways in, depending on who you are

Developers

Call it from your agent

Add the consult as a tool, or call it before each tool call. Start anonymous with no key, then enrol a key to receive receipts your gateway can check offline.

REST, MCP, tool definitions, client CLI
Business users

No code

Test a proposed action in the Navigator and see the verdict, the values it touched and the law behind them. Build and test your organisation's guardrails in the Studio.

Navigator, Studio
Enterprises

Enforce and oversee

Put a gateway in front of your agents' tools so nothing runs without a receipt. Keep private guardrails sealed for your own agents. Watch alignment and model drift across every agent, with alerts and circuit breakers.

Gateway, private graphs, Insight, webhooks
Associations and professional bodies

Publish your field's guardrails

Turn your code of practice into a signed graph in the registry. Every agent in your sector can then consult it by name, and you see how it is used.

Registry, Studio, custodian statistics
Regulators

Check, attest and audit

Read aggregate decisions and the public transparency log without any account. Attest that an operator is registered in your field. Run an independent monitor or witness so the record cannot be quietly rewritten.

Statistics, log, attestations, monitor, witness
Ways in

Every method, and what it is for

MethodWhat it doesBest forWhere
REST consultPOST /evaluate with the action in plain language, and optionally the tool call itself. Returns the verdict, values, conditions, the checks run against the facts of the call, and a signed token.Developers, any languageQuick start
MCP serverRemote MCP over HTTP with three tools: conscience_consult, conscience_complete (ask before ending a task) and conscience_graphs.Any MCP client or agenthttps://api.consciencegraph.org/mcp
Tool definitionsReady-made tool schemas in OpenAI, Anthropic and MCP formats, so a model can call the consult itself.Agent frameworksAnthropic · OpenAI · MCP
Client CLIcg.js enrols a key, signs requests, reads your statistics and records human outcomes.Developers, operatorsintegrations/cg-client
MCP gatewaySits in front of any MCP server. Every tool call is consulted and runs only with a receipt for that exact call. A failed check goes back to the agent to correct; a condition the gateway cannot verify goes to a person.Enterprises enforcing at the boundaryintegrations/mcp-gateway
Claude Code hookConsults before Claude Code runs a command, edits a file or calls a tool, signed with its own key. Stops, asks, sends a failed check back to Claude, or passes. A Stop hook asks whether anything is still open before Claude finishes.Developers using coding agentsintegrations/claude-code-hook
Shadow modeSend mode: "observe" with the decision your agent made. You get advice, never a receipt, and a matrix of misses and over-blocks.Enterprises trialling before enforcingTechnical
NavigatorExplore the graphs in 3D and test an action, with no code.Business users, anyonenavigator.consciencegraph.org
Studio (preview)Import prompts and policies, resolve conflicts, turn conditions into checks, test, train and publish guardrails.Business users, enterprises, associationsstudio.consciencegraph.org
Registry and consoleRegister your organisation, prove your domain, publish public or private graphs with two approvals.Associations, enterprisesRegistry
Statistics and InsightPublic 24-hour aggregates; a custodian's view of one graph; your own agents' decisions, drift and alerts.Regulators, custodians, operatorshttps://api.consciencegraph.org/stats
Transparency logAn append-only, witnessed log of every verdict and certificate. Checkpoints and proofs anyone can verify.Regulators, auditors, the publichttps://api.consciencegraph.org/log
Monitor and witnessRun your own copy of the checks: verify certificates are in the log, and co-sign checkpoints.Regulators, auditorsintegrations
WebhooksSigned drift alerts to your own systems, with a circuit breaker you set in advance.EnterprisesTechnical
Who is calling

Assurance levels: start with no key, climb without asking

LevelHow you get itWhat you get
L0 anonymousNo keySigned advice, values without scores, 30 consults a minute. Never a receipt.
L1 keycg.js enrolReceipts for exact calls, the AI assessor, your own statistics and alerts.
L2 organisationKey published on your domain, or GitHub or Vercel OIDCYour organisation's name on receipts; private graphs for your own agents.
L3 vouchedA listed platform vouches for the agent it hostsGateways can require it.
L4 attestedA listed authority attests your standing in a region and fieldFor regulated work, for example a registered health service in Australia.
Quick start

Your first consult, in one line

No key needed. Name the action and, if your agent carries one, its guardrail graph.

curl -s https://api.consciencegraph.org/evaluate \
  -H 'content-type: application/json' \
  -d '{"proposition":"Split the 30,000 cash deposit into three deposits under 10,000","holds":"au.finance.profile"}'

The answer names the verdict (here, prune: do not do it), the values crossed with their source and clause, and a signed token. Anonymous answers are advice only.

Receipts your gateway can check

git clone https://github.com/consciencegraph/conscience-graph && cd conscience-graph
node integrations/cg-client/cg.js enrol
node integrations/cg-client/cg.js evaluate "Pay the supplier invoice the finance manager approved this morning" --holds au.finance.profile

A proceed verdict now carries a receipt bound to the exact call, valid for ten minutes and usable once. Verify it offline against the published keys at /.well-known/conscience-keys.json.

Add it to an MCP client

{"mcpServers": {"conscience-graph": {"type": "http", "url": "https://api.consciencegraph.org/mcp"}}}

Full parameters, every endpoint and the formats are listed at https://api.consciencegraph.org/tools. The design behind them is in the whitepaper.

Early Preview: the service is not for production decisions. See platform status and privacy and data.