Synthex Forge — x402 Paid Agent Services

Record Evidence Corpus

record_evidence_corpus

Destructive

Anchor a document set. use it rather than create_audit_evidence_package for corpus, not audit evidence package; an object with 55 fields including anchorMethod, anchor_method. $2 USDC.

Input Schema

Name	Required	Description	Default
`merkle`	No	The merkle this operation operates on. See the schema for its type and whether it is required.	sha256
`notarise`	No	The notarise this operation operates on. See the schema for its type and whether it is required.
`documents`	No	The documents this operation operates on. See the schema for its type and whether it is required.
`anchored_at`	No	The anchored at this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`llm`	No	The `llm` field of the response.
`hash`	No	The `hash` field of the response.
`kind`	No	The `kind` field of the response.
`name`	No	The `name` field of the response.
`side`	No	The `side` field of the response.
`clock`	No	The `clock` field of the response.
`index`	No	The `index` field of the response.
`key_id`	No	The `key_id` field of the response.
`leaves`	No	The `leaves` field of the response.
`profile`	No	The `profile` field of the response.
`verdict`	Yes	The decision this tool returned.
`rootHash`	No	The `rootHash` field of the response.
`siblings`	No	The `siblings` field of the response.
`verdicts`	No	The `verdicts` field of the response.
`leafCount`	No	The `leafCount` field of the response.
`leaf_hash`	No	The `leaf_hash` field of the response.
`leaf_name`	No	The `leaf_name` field of the response.
`notarised`	No	The `notarised` field of the response.
`root_hash`	No	The `root_hash` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_by`	No	The key id that signed the answer.
`anchoredAt`	No	The `anchoredAt` field of the response.
`hash_basis`	No	The `hash_basis` field of the response.
`leaf_count`	No	The `leaf_count` field of the response.
`leaf_index`	No	The `leaf_index` field of the response.
`public_key`	No	The `public_key` field of the response.
`sort_order`	No	The `sort_order` field of the response.
`anchored_at`	No	The `anchored_at` field of the response.
`bytes_count`	No	The `bytes_count` field of the response.
`methodology`	No	The `methodology` field of the response.
`anchorMethod`	No	The `anchorMethod` field of the response.
`notarisation`	No	The `notarisation` field of the response.
`proofExample`	No	The `proofExample` field of the response.
`anchor_method`	No	The `anchor_method` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`how_to_verify`	No	The `how_to_verify` field of the response.
`leaf_preimage`	No	The `leaf_preimage` field of the response.
`mismatch_rule`	No	The `mismatch_rule` field of the response.
`notarise_note`	No	The `notarise_note` field of the response.
`odd_leaf_rule`	No	The `odd_leaf_rule` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`proof_example`	No	The `proof_example` field of the response.
`leaf_separator`	No	The `leaf_separator` field of the response.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`merkleAlgorithm`	No	The `merkleAlgorithm` field of the response.
`profile_version`	No	Version of the answer profile.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`merkle_algorithm`	No	The `merkle_algorithm` field of the response.
`notariseRequested`	No	The `notariseRequested` field of the response.
`methodologyVersion`	No	The `methodologyVersion` field of the response.
`notarise_requested`	No	The `notarise_requested` field of the response.
`methodology_version`	No	Version of the method that produced the answer.
`signature_algorithm`	No	The `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed57 schema fields changedOct 31, 2026

addedOutput schema / properties / anchorMethod

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

addedOutput schema / properties / anchor_method

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

addedOutput schema / properties / anchoredAt

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

addedOutput schema / properties / anchored_at

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

addedOutput schema / properties / bytes_count

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

addedOutput schema / properties / canonicalization

Added value: +{
+  "description": "The canonicalisation rule the digest was computed under.",
+  "type": "string"
+}

addedOutput schema / properties / clock

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / evidence_core

Added value: +{
+  "description": "The canonical, signed core of the answer — the payload the signature covers.",
+  "type": "object"
+}

addedOutput schema / properties / hash

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

addedOutput schema / properties / hash_basis

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

addedOutput schema / properties / how_to_verify

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

addedOutput schema / properties / index

Added value: +{
+  "description": "The `index` 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 / kind

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

addedOutput schema / properties / leafCount

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

addedOutput schema / properties / leaf_count

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

addedOutput schema / properties / leaf_hash

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

addedOutput schema / properties / leaf_index

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

addedOutput schema / properties / leaf_name

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

addedOutput schema / properties / leaf_preimage

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

addedOutput schema / properties / leaf_separator

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

addedOutput schema / properties / leaves

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

addedOutput schema / properties / llm

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

addedOutput schema / properties / merkleAlgorithm

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

addedOutput schema / properties / merkle_algorithm

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

addedOutput schema / properties / methodology

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

addedOutput schema / properties / methodologyVersion

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

addedOutput schema / properties / methodology_version

Added value: +{
+  "description": "Version of the method that produced the answer.",
+  "type": "string"
+}

addedOutput schema / properties / mismatch_rule

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

addedOutput schema / properties / missing_fields

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

addedOutput schema / properties / name

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

addedOutput schema / properties / notarisation

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

addedOutput schema / properties / notariseRequested

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

addedOutput schema / properties / notarise_note

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

addedOutput schema / properties / notarise_requested

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

addedOutput schema / properties / notarised

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

addedOutput schema / properties / odd_leaf_rule

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

addedOutput schema / properties / output_sha256

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "type": "string"
+}

addedOutput schema / properties / profile

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

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / profile_version

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / proofExample

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

addedOutput schema / properties / proof_example

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

addedOutput schema / properties / public_key

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

addedOutput schema / properties / rootHash

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

addedOutput schema / properties / root_hash

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

addedOutput schema / properties / siblings

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

addedOutput schema / properties / side

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

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

addedOutput schema / properties / signature_algorithm

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

addedOutput schema / properties / signed_by

Added value: +{
+  "description": "The key id that signed the answer.",
+  "type": "string"
+}

addedOutput schema / properties / sort_order

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

removedOutput schema / properties / status

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

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verdicts

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

addedOutput schema / required

Added value: +[
+  "evidence_core",
+  "output_sha256",
+  "signature",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare the destructive, non-idempotent, non-open-world profile, so the safety bar is lower. The description adds useful cost context ('$2 USDC') but does not explain what anchoring does to existing data, whether it is reversible, or what permissions are needed. The reference to 'an object with 55 fields including anchorMethod, anchor_method' is opaque and does not clarify behavior.

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?

It is short, but the structure is poor: sentence fragments, inconsistent capitalization ('use it rather than...'), and a trailing clause about '55 fields including anchorMethod, anchor_method' that is unclear and may refer to the output object. Every sentence should earn its place, and this one muddies rather than clarifies.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a destructive, non-idempotent write with zero required parameters, the description should state what gets anchored, what is at risk, and any prerequisites. Only the cost is given; the '55 fields' phrase is ambiguous rather than informative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the schema descriptions are generic boilerplate and the description adds no meaning for the four actual parameters (merkle, notarise, documents, anchored_at). Worse, it mentions `anchorMethod`, which is not among the listed parameters, creating potential confusion rather than adding semantic value.

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 opening clause 'Anchor a document set' gives a specific verb and resource, and the description explicitly distinguishes itself from the sibling `create_audit_evidence_package` by scope (corpus vs. audit evidence package). The grammar is garbled, but an agent can identify what the tool does and which sibling it replaces.

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 routes the agent: use this rather than `create_audit_evidence_package` when the target is a corpus. That is a concrete when-to-use/alternative instruction, though there are no explicit exclusions or preconditions stated.

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.