Runtime Admissibility Core

Verify execution legitimacy before consequence.

A bounded evaluation primitive that checks whether current state, authority, constraints, and consequence boundary still support the requested execution path.

Choose access Run live evaluation Read docs

POST /api/evaluate

{
  "outcome": "inadmissible",
  "admissible": false,
  "admissibility_signals": [
    "authority_not_current",
    "runtime_state_contradiction"
  ],
  "runtime_legitimacy": {
    "state_valid": false,
    "authority_valid": false,
    "action_constrained": true
  },
  "artifact_hash": "sha256:..."
}

State + authority

Checks live state validity and current authority continuity.

Stable outcomes

Returns admissible, conditional, or inadmissible with governance signals.

Audit artifact

Every evaluation returns a deterministic artifact hash for replay and audit lineage.

Commercial access

Infrastructure pricing for runtime consequence.

Access is organized around throughput, retention, replayability, and deployment sensitivity — not seats.

Developer

$49/month

For early integrations, interoperability tests, and prototype systems.

10,000 evaluations/month
Single API key
30-day audit retention
Standard replay artifacts

Infrastructure

$499/month

For production systems requiring runtime admissibility continuity.

250,000 evaluations/month
Multiple API keys
365-day audit retention
Exportable evaluation trail

Enterprise / Sovereignty

Custom

For private, hybrid, sovereign-region, or on-prem evaluation nodes.

Private deployment
Custom retention
White-labeled gateways
Annual contracts

Discuss enterprise

Endpoint

One bounded primitive.

POST https://www.runtime-admissibility.com/api/evaluate

Authentication

Bearer-token protected.

Production customers use issued ra_live tokens. Playground tokens are temporary and should not be used in production.

Authorization header Bearer YOUR_CLIENT_TOKEN

Live playground

Run the admissibility check.

Generate a playground token, submit an execution packet, and inspect the outcome exactly as an integration would receive it.

Execution packet

{
  "packet_id": "demo-001",
  "system_context": {
    "domain": "healthcare",
    "workflow": "discharge-readiness",
    "requested_execution": "prepare-discharge-review"
  },
  "runtime_state": {
    "state_valid": true,
    "validated_conditions": ["patient stable", "oxygen normal"],
    "last_validated_at": "2026-05-20T10:00:00Z"
  },
  "authority_context": {
    "status": "revoked",
    "issuer": "attending-physician",
    "scope": ["discharge-review"]
  },
  "constraint_context": {
    "action_constrained": true,
    "allowed_actions": ["prepare-review"],
    "prohibited_actions": ["final-discharge-without-human-signoff"]
  },
  "consequence_boundary": {
    "level": "high",
    "scope": "clinical-discharge",
    "irreversibility": "moderate"
  },
  "runtime_signals": [
    {
      "source": "nurse-monitor",
      "statement": "oxygen unstable; physician authority revoked",
      "seen_at": "2026-05-20T10:10:00Z"
    }
  ],
  "freshness_policy": {
    "state_stale_after_minutes": 30
  }
}

Token

No playground token generated yet.

Evaluation result

No evaluation yet.

Enterprise access

Need private deployment, high retention, or sovereign controls?

Send a short note and the access team will follow up with deployment, retention, compliance, and throughput options.

Examples

Request patterns.

curl -X POST https://www.runtime-admissibility.com/api/evaluate \
  -H "Authorization: Bearer YOUR_CLIENT_TOKEN" \
  -H "Content-Type: application/json" \
  -d @packet.json

Invoke-RestMethod `
  -Uri "https://www.runtime-admissibility.com/api/evaluate" `
  -Method POST `
  -ContentType "application/json" `
  -Headers @{ Authorization = "Bearer YOUR_CLIENT_TOKEN" } `
  -Body $body

const response = await fetch("https://www.runtime-admissibility.com/api/evaluate", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_CLIENT_TOKEN",
    "Content-Type": "application/json"
  },
  body: JSON.stringify(packet)
});

const result = await response.json();