Synthex Forge — x402 Paid Agent Services

Get Settlement Route Advice

get_settlement_route_advice

Read-onlyIdempotent

Advise on the settlement route. use it rather than create_settlement_receipt for settlement route advice, not settlement receipt; an object with 55 fields including alternatives, blocking_constraint. $0.5 USDC.

Input Schema

Name	Required	Description
`asset`	No	The asset this operation operates on. See the schema for its type and whether it is required.
`urgency`	No	The urgency this operation operates on. See the schema for its type and whether it is required.
`amount_usd`	No	The amount in USD. The settlement rail converts it to the exact atomic amount.
`rail_table`	No	The rail table this operation operates on. See the schema for its type and whether it is required.
`constraints`	No	Hard constraints the result must respect.
`destinations`	No	The destinations 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.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`rail`	No	The `rail` field of the response.
`clock`	No	The `clock` field of the response.
`hours`	No	The `hours` field of the response.
`key_id`	No	The `key_id` field of the response.
`reason`	No	Why the verdict was reached.
`minutes`	No	The `minutes` field of the response.
`network`	No	The `network` field of the response.
`profile`	No	The `profile` field of the response.
`verdict`	Yes	The decision this tool returned.
`excluded`	No	The `excluded` field of the response.
`verdicts`	No	The `verdicts` field of the response.
`immediate`	No	The `immediate` 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.
`tradeoffs`	No	The `tradeoffs` field of the response.
`urgencies`	No	The `urgencies` field of the response.
`constraint`	No	The `constraint` field of the response.
`fee_models`	No	The `fee_models` field of the response.
`fee_source`	No	The `fee_source` field of the response.
`public_key`	No	The `public_key` field of the response.
`max_fee_usd`	No	The `max_fee_usd` field of the response.
`methodology`	No	The `methodology` field of the response.
`recommended`	No	The `recommended` field of the response.
`alternatives`	No	The `alternatives` field of the response.
`destinations`	No	The `destinations` field of the response.
`confirmations`	No	The `confirmations` 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.
`fee_delta_usd`	No	The `fee_delta_usd` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`seconds_delta`	No	The `seconds_delta` field of the response.
`exclusion_rule`	No	The `exclusion_rule` field of the response.
`fee_provenance`	No	The `fee_provenance` field of the response.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`profile_version`	No	Version of the answer profile.
`railTableSource`	No	The `railTableSource` field of the response.
`urgency_mapping`	No	The `urgency_mapping` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`exclusion_counts`	No	The `exclusion_counts` field of the response.
`estimated_fee_usd`	No	The `estimated_fee_usd` field of the response.
`min_confirmations`	No	The `min_confirmations` field of the response.
`rail_table_source`	No	The `rail_table_source` field of the response.
`constraintsApplied`	No	The `constraintsApplied` field of the response.
`methodologyVersion`	No	The `methodologyVersion` field of the response.
`blocking_constraint`	No	The `blocking_constraint` field of the response.
`constraints_applied`	No	The `constraints_applied` 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.
`default_rail_table_source`	No	The `default_rail_table_source` field of the response.
`blocking_constraint_detail`	No	The `blocking_constraint_detail` field of the response.
`estimated_settlement_seconds`	No	The `estimated_settlement_seconds` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed57 schema fields changedOct 31, 2026

addedOutput schema / properties / alternatives

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

addedOutput schema / properties / blocking_constraint

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

addedOutput schema / properties / blocking_constraint_detail

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

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

addedOutput schema / properties / constraint

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

addedOutput schema / properties / constraintsApplied

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

addedOutput schema / properties / constraints_applied

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

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

addedOutput schema / properties / destinations

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

addedOutput schema / properties / estimated_fee_usd

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

addedOutput schema / properties / estimated_settlement_seconds

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

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

addedOutput schema / properties / exclusion_counts

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

addedOutput schema / properties / exclusion_rule

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

addedOutput schema / properties / fee_delta_usd

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

addedOutput schema / properties / fee_models

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

addedOutput schema / properties / fee_provenance

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

addedOutput schema / properties / fee_source

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

addedOutput schema / properties / hours

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

addedOutput schema / properties / immediate

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

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

addedOutput schema / properties / max_fee_usd

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

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

addedOutput schema / properties / minutes

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

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

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

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 / public_key

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

addedOutput schema / properties / rail

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

addedOutput schema / properties / railTableSource

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

addedOutput schema / properties / rail_table_source

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

addedOutput schema / properties / reason

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

addedOutput schema / properties / recommended

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

addedOutput schema / properties / seconds_delta

Added value: +{
+  "description": "The `seconds_delta` 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"
+}

removedOutput schema / properties / status

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

addedOutput schema / properties / tradeoffs

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

addedOutput schema / properties / urgencies

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

addedOutput schema / properties / urgency_mapping

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

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-derivable context: it returns an object with 55 fields including `alternatives` and `blocking_constraint`, and it costs $0.5 USDC — the cost disclosure in particular is material for an agent deciding whether to call it.

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?

It is short, but it is one run-on clause chain mixing purpose, sibling exclusion, return shape and price with semicolons. The pricing and sibling distinction are buried rather than front-loaded, and "not settlement receipt" is redundant with the preceding clause.

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 6-parameter, closed-world, idempotent read tool with an output schema, the description covers what it does, when to prefer it over the sibling, that output is rich (55 fields) and that there is a per-call cost. What is missing is any hint of how `amount_usd`, `rail_table` and `constraints` shape the advice.

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 baseline is 3, and the description adds nothing about individual parameters such as `destinations`, `constraints` or `urgency` — no example values, no interaction rules. Several schema descriptions are boilerplate ("See the schema for its type and whether it is required"), so the doc burden shifts to the schema rather than the description.

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?

"Advise on the settlement route" gives a specific verb+resource, and the sentence explicitly contrasts it with `create_settlement_receipt`, so an agent can tell it apart from the receipt-creating sibling. The awkward phrasing ("for settlement route advice, not settlement receipt") makes it slightly harder to parse but the intent survives.

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 names the alternative explicitly ("use it rather than `create_settlement_receipt`") which is the key routing decision here. It stops short of stating when in a workflow the advice should be requested (e.g. before calling `execute_route`) or any preconditions, so it is clear but not exhaustive.

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.