agent-embassy

Trust Report

trust_report

Idempotent

Use trust_report when you need a buy/don't-buy decision on a candidate x402 endpoint: the Embassy probes it unpaid (no payment header, zero spend) and returns a signed PROCEED, VERIFY_FIRST, or DO_NOT_PAY verdict — a decision, never a score. 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/trust/report.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	HTTPS URL of the candidate x402 endpoint to probe (max 2000 chars; no credentials in URL). Probed unpaid via GET, falling back to an empty-body POST when GET returns 404/405
`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.

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.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / agent_wallet

Removed value: -{
-  "description": "Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization.",
-  "type": "string"
-}

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."

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"dev mode only"New value: +"Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization."

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 / url / description

Added value: +"HTTPS URL of the candidate x402 endpoint to probe (max 2000 chars; no credentials in URL). Probed unpaid via GET, falling back to an empty-body POST when GET returns 404/405"

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."New value: +"dev mode only"

removedInput schema / properties / idempotency_key / description

Removed value: -"Client-generated UUID; retries return the original receipt"

removedInput schema / properties / url / description

Removed value: -"HTTPS URL of the candidate x402 endpoint to probe (public hosts only; private IPs refused)"

AddedSep 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavioral details: the tool is paid at $0.25 USDC on Base or Arbitrum One, requires an x402 v2 PAYMENT-SIGNATURE header, probes the target unpaid via GET with fallback to POST, and returns a signed verdict. It also explains idempotency behavior consistently with idempotentHint=true, including key-scoping and first-request-wins semantics.

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 yet information-dense, front-loading the purpose before invocation details. Every sentence adds value: usage trigger, verdict semantics, payment mechanics, cost, networks, and the paid URL, with no filler or repetition.

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?

For a paid, externally invoked tool, the description supplies all necessary call mechanics: destination URL, required payment signature header, cost, supported networks, and an output verdict type. Since an output schema exists, the description does not need to enumerate return fields, and the included docs link covers deeper protocol details.

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 description coverage is 100%, so the parameters url and idempotency_key are already fully documented in the schema. The tool description adds no extra parameter-level meaning beyond the schema's own descriptions, so the baseline score of 3 is appropriate.

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 states a specific action and resource: a buy/don't-buy decision on a candidate x402 endpoint, probed by the Embassy and returning PROCEED, VERIFY_FIRST, or DO_NOT_PAY. 'A decision, never a score' sharpens the boundary against scoring-style verification siblings, making the tool's identity unambiguous.

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?

The opening sentence gives an explicit trigger condition: 'Use trust_report when you need a buy/don't-buy decision on a candidate x402 endpoint.' It also clarifies the output is a verdict, not a score, and notes the paid nature of the call. It does not explicitly name alternative tools or state when-not-to-use, but the context is clear enough for correct selection.

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.