agent-embassy

Assurance Check

assurance_check

Idempotent

Use assurance_check when you need a go/no-go verdict BEFORE an agent acts on a provider: the Embassy probes the provider unpaid (no payment header, zero spend) and returns a signed ALLOW, ALLOW_WITH_RESTRICTIONS, ASK_HUMAN, REVERIFY, REROUTE, or QUARANTINE decision. UNVERIFIED is the honest default for unknowns — never a smear, never a badge. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/assurance/check.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	The action the agent intends to take, e.g. 'transfer' (required, max 200 chars)
`context`	No	Optional free-text context for the assessment (truncated to 2000 chars)
`amount_usdc`	Yes	Amount at stake, as a positive decimal string, e.g. '0.25'
`idempotency_key`	Yes	Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.
`provider_endpoint`	Yes	HTTPS URL of the provider to assess (max 2000 chars; no credentials in URL)
`permissions_requested`	Yes	Permissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. verified_check
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.15"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."

Changed6 schema fields changedSep 24, 2026

addedInput schema / properties / action / description

Added value: +"The action the agent intends to take, e.g. 'transfer' (required, max 200 chars)"

addedInput schema / properties / amount_usdc / description

Added value: +"Amount at stake, as a positive decimal string, e.g. '0.25'"

addedInput schema / properties / context / description

Added value: +"Optional free-text context for the assessment (truncated to 2000 chars)"

addedInput schema / properties / idempotency_key / description

Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."

addedInput schema / properties / permissions_requested / description

Added value: +"Permissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars"

addedInput schema / properties / provider_endpoint / description

Added value: +"HTTPS URL of the provider to assess (max 2000 chars; no credentials in URL)"

AddedSep 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description goes well beyond the idempotentHint and readOnlyHint annotations: it reveals the probe is unpaid, the response is signed, the semantic of UNVERIFIED, the x402 payment header requirement, the cost, and the target URL. This gives the agent a realistic model of the tool's behavior with no contradiction against annotations.

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

Conciseness4/5

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

The description is dense and front-loaded with the most important usage condition, followed by behavior, protocol, and payment details. It is longer than strictly necessary due to the URL and docs link, but every sentence contributes operational information an agent needs.

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 output schema, idempotency info in the parameter schema, and annotations, the description completes the picture: it gives the endpoint, payment amount and chains, required header, decision vocabulary, and honest-default behavior. An agent has enough information to invoke and interpret the tool correctly.

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?

The input schema has 100% description coverage for all six parameters, so the schema already carries the semantic load. The description adds invocation-level context (endpoint, payment, header) but does not add per-parameter meaning beyond what the schema documents, so a baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool's purpose: produce a go/no-go verdict before an agent acts on a provider, and lists the exact decision values. It is more specific than a vague 'check' but does not explicitly contrast sibling tools like preflight_check or verified_check.

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

Usage Guidelines4/5

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

It explicitly says when to use the tool ('when you need a go/no-go verdict BEFORE an agent acts on a provider'), which is a strong usage condition. However, it does not mention exclusions or alternatives, so the guidance is complete on the 'when' but not on the 'when not' side.

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

All agent-embassy 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.