Verification API
Ship verification, delegation, and operational safety checks behind a single API surface. Designed for teams that need auditable responses, clear access tiers, and integration-ready workflows.
Operational Flow
A compact control layer for validating identity, enforcing delegation rules, and returning structured status signals to your applications.
request → verification → policy → response
Designed for stable payloads, predictable controls, and developer-facing auditability.
Capabilities
Use the platform to verify actors, inspect routing outcomes, and integrate status-aware controls into higher-level systems.
| Capability | Output | Typical Use |
|---|---|---|
| Identity verification | verified | denied | Agent registration and request gating |
| Delegation review | accepted | flagged | Task routing and chain-of-control checks |
| Policy evaluation | pass | remediate | Safety controls and operational guardrails |
| Drift reporting | stable | investigate | Monitoring service health and response quality |
| Schema-ready payloads | json | Client apps, dashboards, and automations |
| Access tiers | free | research-pro | enterprise | Scaling from prototypes to production |
Response Preview
Preview the kinds of structured responses the Verification API returns without exposing implementation details on the marketing surface.
A typical response for identity and policy checks.
A sample tier and quota profile for enabled clients.
Integration
Start from the API documentation, provision credentials, and wire verification responses into your existing services.
# Review the published API surface curl https://aaaa-nexus.atomadictech.workers.dev/openapi.json \ -H "Authorization: Bearer YOUR_KEY" # Call your provisioned verification endpoint curl https://aaaa-nexus.atomadictech.workers.dev/v1/identity/verify
const res = await fetch( 'https://aaaa-nexus.atomadictech.workers.dev/v1/identity/verify', { headers: { 'Authorization': `Bearer ${key}` } } ); const result = await res.json(); console.log(result.status); // verified
import requests resp = requests.get( "https://aaaa-nexus.atomadictech.workers.dev/v1/identity/verify", headers={"Authorization": f"Bearer {key}"} ) data = resp.json() print(data["checks"])
import { AethelNexus } from 'aethel-nexus-sdk'; const nexus = new AethelNexus({ apiKey: key }); const verification = await nexus.identity.verify(); console.log(verification.decision);
Pricing
From prototyping to production workloads with managed verification and routing controls.
$0 / mo
$29 / mo
Custom
Status Badge
Embed a verification-ready badge in your documentation to show that requests pass through a managed control layer.
<!-- Embed in your docs --> <a href="https://aaaa-nexus.atomadictech.workers.dev/codex"> <img src="https://img.shields.io/badge/Verification-Ready-F5A623?style=flat-square" alt="Verification Ready" /> </a>
Open Verification
The formal proofs behind every Aethel Nexus guarantee are open — 29 Lean 4 theorems, zero sorry, zero axioms beyond Lean’s kernel. You don’t have to take our word for it.
sorry · proofs/AethelNexus/CodexConstants.lean
✓ 21 compile-time assertions · Rust aethel-constants crate
✓ Independent verification suite · 15/15 checks pass · run against the open-source proofs
✓ Omega Singularity identity · formally closed, no open terms
The mathematical constants powering this API are formally proven in Lean 4. Every claim is machine-checked — no trust required.