Pre-execution policy gate for consequential agent actions with durable trust receipts.
Scored across 9 tools
Most tools have clear, distinct responsibilities: verify_* handles verification, get_* handles retrieval, and metadata tools serve discovery. The three discovery-oriented tools overlap somewhat in intent, but their descriptions explicitly differentiate use cases, so selection should be reliable.
All tool names use the oracle. prefix and lowercase snake_case, with verify_* and get_* conveying actions. The metadata tools break the verb_noun pattern by using bare nouns such as agent_card and service_descriptor, but this is a minor and readable deviation.
Nine tools cover the server's core concerns—discovery, pricing, verification, batch, legacy, and trust receipt validation—without unnecessary bloat. Each tool maps to a distinct user need and the count is well within the ideal range.
The set covers the full lifecycle of the oracle's purpose: pricing before onboarding, discovery for integration, action/batch/legacy verification, receipt retrieval, and signature validation. No obvious dead ends remain for the stated risk-oracle domain.
Read-only A2A Agent Card with agent identity, security scheme, capabilities, and skills. Use it when selecting or integrating InterAI through A2A; use oracle.service_descriptor for general service metadata or oracle.discovery_bundle for complete bootstrap context.
Inputs: no named parameters. Returns: InterAI A2A Agent Card returned as machine-readable JSON.
Read-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.
Inputs: no named parameters. Returns: Complete machine-readable InterAI integration bundle for bootstrap and handoff.
Read-only public metadata for costs, trial availability, idempotency, and top-up or payment paths. Use it before budgeting or onboarding; it does not evaluate risk or create a trust receipt.
Inputs: no named parameters. Returns: Current public InterAI pricing, onboarding, x402, top-up, trial, and idempotenc…
Read-only lookup of the canonical public representation and signature metadata for a trust receipt that already exists. Supply receipt_id. It does not create or re-run a decision; use oracle.verify_trust_receipt_signature when the goal is signature validation.
Inputs: receipt_id (required). Returns: Canonical public representation, signature metadata, and trust fields for an ex…
Read-only general service descriptor with identity, endpoints, billing, trust, and supported agent protocols. Use it to inspect service-level integration metadata; use oracle.agent_card for A2A skills or oracle.discovery_bundle for the complete bootstrap package.
Inputs: no named parameters. Returns: Focused InterAI service-level metadata covering identity, endpoints, billing, t…
Primary tool for one concrete proposed autonomous action before it executes. This authenticated prepaid verification may consume account balance and records a signed trust receipt; InterAI evaluates the proposal but does not execute or modify the proposed external action. Reuse idempotency_key only when retrying the same logical request to avoid duplicate billing. Returns allow, review_required, or block with policy signals. Use oracle.verify_batch for multiple independent items and oracle.verify_response only for legacy prompt/response compatibility.
Inputs: action (required), use_case (required), mode, domain, +6 more. Returns: Successful InterAI single-verification result. The unstructured content field c…
Use for multiple independent legacy or autonomous verification items in one authenticated prepaid call (1 to 100). The batch may consume account balance and records one trust receipt per item; InterAI does not execute any proposed external action. Reuse idempotency_key only for the same logical batch retry. For one proposed action, use oracle.verify_autonomous_action instead.
Inputs: items (required), idempotency_key. Returns: Successful InterAI batch verification result. The unstructured content field ca…
Legacy compatibility entry point for existing clients. This authenticated prepaid verification may consume account balance and records a trust receipt, but it does not execute any proposed external action. Supply exactly one contract: prompt + response, or use_case + action; never mix them. Reuse idempotency_key only for the same logical retry. For new action preflight use oracle.verify_autonomous_action; use oracle.verify_batch for multiple items.
Inputs: mode, action, domain, policy, +8 more. Returns: Successful InterAI single-verification result. The unstructured content field c…
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.
Inputs: signature (required), receipt, receipt_id, signature_alg, +1 more. Returns: Service-side signature-validation result for an existing InterAI trust receipt.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Authorize AI agent tool calls before they run: policy-as-code, human approval, signed receipts.
Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools.
Add one secure layer between your agents and this server.
