agent-embassy

Verified Check

verified_check

Idempotent

Verify a web claim and get a signed, re-checkable Outcome Receipt — machine-verifiable proof of delivery for agent commerce. The Embassy fetches your HTTPS URL once, server-side, and checks it against your conditions: HTTP status, a body substring, or a JSON field value. The receipt records the full transcript — final URL, status, timing, body SHA-256, per-condition pass/fail — so anyone can re-verify. $0.15 per check via x402. Fully automated, no human review.

MONETIZED VIA x402 — this tool is not callable for free. POST https://agent-embassy.fly.dev/v1/check/verify with an x402 payment ($0.15, USDC on Base). Input schema: {"type":"object","properties":{"url":{"type":"string","description":"HTTPS URL to fetch (public hosts only; private IPs refused)"},"expect_status":{"type":"number","description":"Expected HTTP status of the final response (default 200)"},"expect_body_contains":{"type":"string","description":"Substring that must appear in the response body"},"expect_json_path":{"type":"string","description":"Dot path into a JSON body, e.g. 'data.ok'"},"expect_json_equals":{"description":"Expected value at expect_json_path (compared as JSON)"},"idempotency_key":{"type":"string","description":"Client-generated UUID; retries return the original receipt"},"agent_wallet":{"type":"string","description":"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."}},"required":["url","idempotency_key"]}

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	HTTPS URL to fetch (public hosts only; private IPs refused)
`agent_wallet`	No	DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used.
`expect_status`	No	Expected HTTP status of the final response (default 200)
`idempotency_key`	Yes	Client-generated UUID; retries return the original receipt
`expect_json_path`	No	Dot path into a JSON body, e.g. 'data.ok'
`expect_json_equals`	No	Expected value at expect_json_path (compared as JSON)
`expect_body_contains`	No	Substring that must appear in the response body

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 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "description": "Settlement asset",
+      "type": "string"
+    },
+    "facilitator": {
+      "description": "x402 facilitator",
+      "type": "string"
+    },
+    "how": {
+      "description": "How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header",
+      "type": "string"
+    },
+    "networks": {
+      "description": "EVM CAIP-2 network ids accepted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "paid_url": {
+      "description": "x402-paid HTTPS URL to POST the tool inputs to",
+      "type": "string"
+    },
+    "payment_required": {
+      "const": true,
+      "description": "Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.",
+      "type": "boolean"
+    },
+    "price": {
+      "description": "Exact price, e.g. \"$0.15\"",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Tool name, e.g. verified_check",
+      "type": "string"
+    }
+  },
+  "required": [
+    "payment_required",
+    "tool",
+    "paid_url",
+    "price",
+    "networks",
+    "asset",
+    "facilitator",
+    "how"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedSep 21, 2026

addedInput schema / properties / agent_wallet / description

Added value: +"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."

addedInput schema / properties / expect_body_contains / description
```
Added value: +"Substring that must appear in the response body"
```

addedInput schema / properties / expect_json_equals / description

Added value: +"Expected value at expect_json_path (compared as JSON)"

addedInput schema / properties / expect_json_path / description
```
Added value: +"Dot path into a JSON body, e.g. 'data.ok'"
```

addedInput schema / properties / expect_status / description

Added value: +"Expected HTTP status of the final response (default 200)"

addedInput schema / properties / idempotency_key / description

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

addedInput schema / properties / url / description

Added value: +"HTTPS URL to fetch (public hosts only; private IPs refused)"

First observedSep 21, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description goes far beyond the annotations by disclosing: the server-side fetch happens once, the receipt records the full transcript with SHA-256 and per-condition results, the service is monetized via x402 ($0.15), it is fully automated with no human review, private IPs are refused, and idempotency_key retries return the original receipt. This is rich behavioral context that annotations alone do not convey.

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

Conciseness2/5

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

The first paragraph is tight and front-loaded, but the second 'MONETIZED VIA x402' block repeats the endpoint and then dumps the full input schema, which is already provided separately. This duplication bloats the description and violates the principle that every sentence should earn its place. The same information could be conveyed in half the length.

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

Completeness4/5

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

For a paid, idempotent verification tool, the description covers purpose, conditions, output receipt contents, payment requirement, endpoint, host restrictions, idempotency behavior, and dev-mode wallet usage. The output schema exists and covers return values, so the description need not detail them. Only minor items like rate limits or explicit error behavior are absent, which are not critical for correct invocation.

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 schema already documents every parameter. The description adds some context by grouping conditions (status, body substring, JSON field) and explaining that idempotency_key returns the original receipt on retry. However, it also duplicates the entire input schema inline, which adds no new meaning beyond the structured field. The marginal value over the schema is moderate.

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 opens with a specific verb and resource: 'Verify a web claim and get a signed, re-checkable Outcome Receipt.' It then enumerates the exact conditions (HTTP status, body substring, JSON field value), making the tool's function unmistakable. It clearly differentiates from siblings like compute_spot_prices or register_recovery, which have wholly different purposes.

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 description gives clear context for when to use the tool: for agent commerce, machine-verifiable proof of delivery, and automated verification of web claims. It does not explicitly name alternatives or exclusions, but the sibling tools are unrelated in domain, so no routing ambiguity exists. A small gap: no explicit 'use this when, not when' statement.

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.