InterAI Risk Oracle

Verify Trust Receipt Signature

oracle.verify_trust_receipt_signature

Read-onlyIdempotent

Read-only service-side validation of a trust receipt that already exists. Supply signature plus either receipt_id for the canonical server-stored receipt or a caller-supplied receipt object. Returns valid true or false when signing is enabled. Current signatures use HMAC-SHA256 and are service-verifiable by InterAI, not independent offline public-key proofs. It does not evaluate risk or create a receipt; use oracle.get_trust_receipt to retrieve receipt metadata.

Input Schema

TableJSON Schema

Name	Required	Description
`receipt`	No	Optional caller-supplied receipt object, typically evidence received from another agent or system. Either receipt or receipt_id is required.
`signature`	Yes	HMAC-SHA256 signature to validate against the referenced InterAI receipt. Required.
`receipt_id`	No	Optional ID of an existing InterAI trust receipt. InterAI resolves the canonical server-stored record before validating the supplied signature. Either receipt_id or receipt is required.
`signature_alg`	No	Optional signature algorithm declaration. The current supported value is hmac-sha256.
`signed_payload`	No	Optional exact serialized payload that was signed. Supply it when validating externally transported receipt evidence that includes the original signed payload.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`valid`	Yes	Whether the supplied signature matches the referenced stored receipt.
`signature_alg`	Yes	Signature algorithm used by the current InterAI receipt verifier.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "Service-side signature-validation result for an existing InterAI trust receipt.",
+  "properties": {
+    "signature_alg": {
+      "description": "Signature algorithm used by the current InterAI receipt verifier.",
+      "enum": [
+        "hmac-sha256"
+      ],
+      "type": "string"
+    },
+    "valid": {
+      "description": "Whether the supplied signature matches the referenced stored receipt.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "valid",
+    "signature_alg"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedSep 10, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "receipt"
-    ]
-  },
-  {
-    "required": [
-      "receipt_id"
-    ]
-  }
-]New value: +[
+  {
+    "description": "Validate using a caller-supplied receipt object.",
+    "required": [
+      "receipt"
+    ]
+  },
+  {
+    "description": "Validate using the canonical server-stored receipt resolved from receipt_id.",
+    "required": [
+      "receipt_id"
+    ]
+  }
+]

addedInput schema / description

Added value: +"Validate an existing InterAI receipt signature. Provide signature and either receipt_id or receipt; optional signed_payload and signature_alg can further bind the supplied evidence."

addedInput schema / properties / receipt / description

Added value: +"Optional caller-supplied receipt object, typically evidence received from another agent or system. Either receipt or receipt_id is required."

addedInput schema / properties / receipt_id / description

Added value: +"Optional ID of an existing InterAI trust receipt. InterAI resolves the canonical server-stored record before validating the supplied signature. Either receipt_id or receipt is required."

addedInput schema / properties / signature / description

Added value: +"HMAC-SHA256 signature to validate against the referenced InterAI receipt. Required."

addedInput schema / properties / signature_alg / description

Added value: +"Optional signature algorithm declaration. The current supported value is hmac-sha256."

addedInput schema / properties / signed_payload / description

Added value: +"Optional exact serialized payload that was signed. Supply it when validating externally transported receipt evidence that includes the original signed payload."

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context: HMAC-SHA256 current signatures, service-verifiable by InterAI rather than independent offline public-key proofs, and boolean return behavior when signing is enabled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the core purpose, and every sentence adds distinct value: inputs, return behavior, cryptographic caveat, and exclusions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema, output schema, and annotations, the description covers everything needed to invoke the tool correctly: what it validates, which inputs to provide, what it returns, and what it intentionally does not do.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and each parameter already has a solid description including the either/or relationship between receipt and receipt_id. The tool description summarizes the input pattern but does not materially add semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: read-only service-side validation of an existing trust receipt. It also differentiates itself from oracle.get_trust_receipt by explicitly saying it validates rather than retrieves or creates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the required inputs: signature plus either receipt_id or a caller-supplied receipt. It also gives an explicit exclusion ('does not evaluate risk or create a receipt') and points to oracle.get_trust_receipt as the retrieval alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InterAI Risk Oracle tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.