Constitutional Verification API

Review text and prompt-response pairs under the API's earlier runtime profile. Attestation can be a PREVIEW; check the returned status before claiming a chain witness.

"Safety that lives in teams dies when teams dissolve. Safety that lives in infrastructure survives. You cannot fire a Constitution."

What this does

The v1 API reports entropy analysis, a pattern precheck, and an AI scan for submitted text. Its govern route also analyzes the response in a prompt-response pair. Review the returned flags and explanations as an earlier-profile assessment; they do not certify compliance with the ratified Constitution 2.0.

A flag is a finding to review, not proof that a person or model violated a constitutional article. Compare any cited article with the published text and the request's runtime profile.

Base URL

https://api.article11.ai/api/v1

Endpoints

POST/api/v1/evaluate

Submit text for a v1 compatibility assessment and inspect its entropy, scan, and precheck results.

{ "text": "The AI output you want to verify" }

POST/api/v1/govern

Submit a prompt-response pair for separate input and output analysis under the v1 profile.

{ "prompt": "The user's input", "response": "The AI's response to verify" }

POST/api/v1/certify

Request an attestation. The live GET contract describes PREVIEW with chain_anchor:null and no chain_proof until strict chain verification and separate anchored-issuance enablement. A request alone does not prove an IRONLEDGER witness.

{ "prompt": "The user's input", "response": "The AI's response to certify" }

GET/api/v1

API documentation and endpoint discovery.

Try it now

Enter text to evaluate:

Quick start

# Evaluate any text
curl -X POST https://api.article11.ai/api/v1/evaluate \
  -H "Content-Type: application/json" \
  -d '{"text":"Your AI output here"}'

# Verify a prompt+response pair
curl -X POST https://api.article11.ai/api/v1/govern \
  -H "Content-Type: application/json" \
  -d '{"prompt":"User question","response":"AI answer to verify"}'

# Request an attestation; inspect status and chain_anchor before claiming a witness
curl -X POST https://api.article11.ai/api/v1/certify \
  -H "Content-Type: application/json" \
  -d '{"prompt":"User question","response":"AI answer to certify"}'

The five principles

1. Truth over outcome

2. Choice over control

3. Care over exploitation

4. Memory over oblivion

5. Partnership over domination

Access and pricing

Free

Up to 100 anonymous v1 requests/day per network address, subject to live service limits.

No key for this tier; certify can return PREVIEW without a chain witness.

Additional access

Ask first

Availability and terms are not stated here.

Ask whether API-key access or priority routing is offered before relying on it. Contact us to ask about availability and terms.

Custom inquiry

Ask first

Capacity and terms require confirmation.

This page does not promise unlimited use, an SLA, or custom patterns. Contact us to ask about capacity and terms.

Architecture

The Worker routes these v1 API requests and returns separate analysis fields. Evaluate, govern, and certify have different paths; no fixed stage count or current 2.0 enforcement is established by this page. Inspect each response's status, flags, and provenance before relying on it.

The Constitution is CC0. Read it, fork it: article11.ai/constitution

The first IRONLEDGER head-hash proof is attested in Bitcoin block 957,512. Check the latest anchor record for the scheduled run's trigger, timestamp, and status. Verify the anchor yourself.