Synthex Forge — x402 Paid Agent Services

Verify X402 Anchor

verify_x402_anchor

Read-onlyIdempotent

recompute a root from supplied records and check the signature. use it rather than create_x402_anchor for x402 anchor specifically; an object with 8 fields including checks, claimed_root.

Input Schema

Name	Required	Description
`body`	No	The anchor body exactly as it was served (it carries the published corpus_root).
`records`	No	The corpus records the anchor was computed over. The root is recomputed from THESE and compared with the published one.
`manifest`	No	The manifest exactly as it was served.

Output Schema

Name	Required	Description
`valid`	Yes	Whether the artifact verified.
`checks`	No	The individual checks that were run.
`key_id`	No	The `key_id` field of the response.
`reason`	No	Why the verdict was reached.
`claimed_root`	No	The `claimed_root` field of the response.
`claimed_sha256`	No	The `claimed_sha256` field of the response.
`recomputed_root`	No	The `recomputed_root` field of the response.
`recomputed_sha256`	No	The `recomputed_sha256` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 31, 2026

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / claimed_root

Added value: +{
+  "description": "The `claimed_root` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / claimed_sha256

Added value: +{
+  "description": "The `claimed_sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / key_id

Added value: +{
+  "description": "The `key_id` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / recomputed_root

Added value: +{
+  "description": "The `recomputed_root` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / recomputed_sha256

Added value: +{
+  "description": "The `recomputed_sha256` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / valid

Added value: +{
+  "description": "Whether the artifact verified.",
+  "type": "boolean"
+}

addedOutput schema / required
```
Added value: +[
+  "valid"
+]
```

AddedOct 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful mechanic that the root is recomputed from the supplied records and compared against the published one, but it does not say what happens on mismatch (raised error vs. a false `checks` field), which is the key behavioral unknown for a verification tool.

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

Conciseness3/5

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

Two short sentences with no filler, and the action is front-loaded. However, the trailing fragment 'an object with 8 fields including checks, claimed_root' is poorly integrated and largely redundant given that an output schema already exists, so part of the text does not earn its place.

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

Completeness3/5

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

With a full input schema, a declared output schema and complete annotations, most of the burden is already carried. The description supplies the core verification mechanic, but for a tool whose entire value is detecting mismatch it omits failure semantics and any hint about how strict the comparison is.

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%, including the important note that the root is recomputed from THESE records, so the schema does the heavy lifting. The description only restates 'supplied records' and adds no format, ordering, or completeness expectations beyond what the schema already says. Baseline 3 applies.

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?

States a concrete verb sequence (recompute a root from supplied records, check the signature) and names the resource (x402 anchor), which clearly separates it from create_x402_anchor and the other verify_* siblings. It is not quite a 5 because the 'use it rather than create_x402_anchor' clause blends purpose with routing and reads awkwardly.

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

Usage Guidelines3/5

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

It names one alternative (`create_x402_anchor`) as the wrong choice, which is useful routing, but create vs. verify are inherently different operations so this exclusion adds little. There is no guidance on prerequisites (you need the body/manifest exactly as served plus the original records) or on when verification is warranted versus unnecessary.

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

All Synthex Forge — x402 Paid Agent Services 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.