Event shapes
Representative request, decision, receipt, and bundle structures.
A read-only technical preview of requests, decisions, receipts, and verifier evidence. No live keys, no terminal, no private rule tables.
The preview shows the integration shape without exposing live API keys, private infrastructure, production data, or proprietary rule logic.
{
"tool": "ayra.gate.check",
"workflow": "claim_submission",
"checks": [
"authority",
"consent_scope",
"documentation"
],
"payload": "redacted_context_ref"
}
{
"decision": "ALLOW",
"route": "continue",
"receipt": {
"receiptBatch": "55",
"block": "42028382",
"proofId": "0xeaddfebc..."
}
}
workflow, checks, context_refALLOW | BLOCK | ROUTEbatch, block, proof_idbundle, scope, recomputedecision ALLOW
route continue
proof present
review scoped
Only redacted references and salted commitments appear in the public proof path.
The public developer page is intentionally read-only. Partners receive controlled specifications and evaluation materials after scope is approved.
Representative request, decision, receipt, and bundle structures.
No credentials, terminals, production systems, private repositories, or proprietary rule tables.
Teams request evaluation scope before receiving deeper API and verifier materials.
Ayra gives reviewers enough structure to understand the proof path while keeping PHI, raw claims, secrets, and private implementation details out of the browser.