Synthex Forge — x402 Paid Agent Services

Get X402 Quote

get_x402_quote

Read-onlyIdempotent

Cost + landing quote for a target call. use it rather than create_x402_anchor for x402 quote, not x402 anchor; an object with 52 fields including _dt, algorithm. $0.01 USDC.

Input Schema

Name	Required	Description	Default
`request`	No	The request 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.	immediate
`target_url`	Yes	The target url this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`ts`	No	The `ts` field of the response.
`_dt`	No	The `_dt` field of the response.
`note`	No	A note on how the answer was produced.
`rail`	No	The `rail` field of the response.
`risk`	No	The `risk` field of the response.
`rows`	No	The `rows` field of the response.
`asset`	No	The `asset` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`quote`	No	The `quote` field of the response.
`risks`	No	The `risks` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`method`	No	The `method` field of the response.
`pay_to`	No	The `pay_to` field of the response.
`probes`	No	The `probes` field of the response.
`sha256`	No	The `sha256` field of the response.
`target`	No	The `target` field of the response.
`network`	No	The `network` field of the response.
`planned`	No	The `planned` field of the response.
`request`	No	The `request` field of the response.
`urgency`	No	The `urgency` field of the response.
`verdict`	Yes	The decision this tool returned.
`evidence`	No	The `evidence` field of the response.
`severity`	No	The `severity` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`price_usd`	No	The price of the operation that was paid.
`confidence`	No	Confidence in the verdict, 0 to 1.
`instrument`	No	The `instrument` field of the response.
`latency_ms`	No	The `latency_ms` field of the response.
`normalised`	No	The `normalised` field of the response.
`public_key`	No	The `public_key` field of the response.
`window_end`	No	The `window_end` field of the response.
`body_sha256`	No	The `body_sha256` field of the response.
`http_status`	No	The `http_status` field of the response.
`last_402_at`	No	The `last_402_at` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`price_source`	No	The `price_source` field of the response.
`probe_method`	No	The `probe_method` field of the response.
`received_usd`	No	The `received_usd` field of the response.
`window_hours`	No	The `window_hours` field of the response.
`window_start`	No	The `window_start` field of the response.
`amount_atomic`	No	The `amount_atomic` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`profileVersion`	No	Version of the answer profile.
`settle_seconds`	No	The `settle_seconds` field of the response.
`estimated_fee_usd`	No	The `estimated_fee_usd` field of the response.
`settlement_sample`	No	The `settlement_sample` field of the response.
`declared_price_usd`	No	The `declared_price_usd` field of the response.
`declared_prices_usd`	No	The `declared_prices_usd` field of the response.
`observed_prices_usd`	No	The `observed_prices_usd` field of the response.
`estimated_settlement_seconds`	No	The `estimated_settlement_seconds` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed54 schema fields changedOct 31, 2026

addedOutput schema / properties / _dt

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / amount_atomic

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

addedOutput schema / properties / asset

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

addedOutput schema / properties / body_sha256

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

addedOutput schema / properties / confidence

Added value: +{
+  "description": "Confidence in the verdict, 0 to 1.",
+  "type": "number"
+}

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / declared_price_usd

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

addedOutput schema / properties / declared_prices_usd

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

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

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

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

addedOutput schema / properties / http_status

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / last_402_at

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

addedOutput schema / properties / latency_ms

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

addedOutput schema / properties / method

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

addedOutput schema / properties / network

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

addedOutput schema / properties / normalised

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

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

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / pay_to

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

addedOutput schema / properties / planned

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

addedOutput schema / properties / price_source

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

addedOutput schema / properties / price_usd

Added value: +{
+  "description": "The price of the operation that was paid.",
+  "type": "number"
+}

addedOutput schema / properties / probe_method

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

addedOutput schema / properties / probes

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

addedOutput schema / properties / profileVersion

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

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

addedOutput schema / properties / rail

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

addedOutput schema / properties / received_usd

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

addedOutput schema / properties / request

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

addedOutput schema / properties / risk

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

addedOutput schema / properties / risks

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

addedOutput schema / properties / rows

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

addedOutput schema / properties / settle_seconds

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

addedOutput schema / properties / settlement_sample

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

addedOutput schema / properties / severity

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signed_over

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

removedOutput schema / properties / status

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

addedOutput schema / properties / target

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

addedOutput schema / properties / ts

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

addedOutput schema / properties / urgency

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

addedOutput schema / properties / value

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / window_end

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

addedOutput schema / properties / window_hours

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

addedOutput schema / properties / window_start

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.5/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 behavior, so the safety profile is covered. The description adds that the return is an object with 52 fields including `_dt` and `algorithm`, plus a cost mention ('$0.01 USDC'), but it is unclear whether that cost is the quoted price or the fee for making the call, and no payment or auth requirements are described.

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 and front-loads the purpose, but the second sentence is a fragmented run-on with strained punctuation ('...not x402 anchor; an object with 52 fields including _dt, algorithm. $0.01 USDC.'), which makes it harder to parse than necessary.

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?

An output schema exists, so return values need not be fully explained, and annotations cover safety. The description still leaves material ambiguity around what 'landing quote' means, how `request` and `urgency` affect the quote, and whether the USDC figure is a price or a fee.

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%, which sets a baseline of 3. The schema descriptions themselves are boilerplate ('The target url this operation operates on...'), and the tool description adds no semantics for `target_url`, `request`, or `urgency` beyond what is already stated.

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 description states a specific output ('Cost + landing quote for a target call') and explicitly distinguishes the tool from the sibling create_x402_anchor ('for x402 quote, not x402 anchor'). However, 'landing quote' and 'target call' are jargon that an agent may not fully understand without opening the schema.

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 names the alternative to use instead ('use it rather than `create_x402_anchor`') and clarifies the selection condition ('for x402 quote, not x402 anchor'). It lacks guidance on when a quote is required versus other x402 operations such as verification or indexing.

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.