Synthex Forge — x402 Paid Agent Services

Get Payment Deadline

get_payment_deadline

Read-onlyIdempotent

Will this payment settle inside my deadline?. use it rather than settle_conditional_payment for payment deadline, not conditional payment; an object with 29 fields including _time_dependent, algorithm. $0.05 USDC.

Input Schema

Name	Required	Description
`rail`	Yes	The rail this operation operates on. See the schema for its type and whether it is required.
`network`	Yes	The network this operation operates on. See the schema for its type and whether it is required.
`deadline`	Yes	The deadline, as an ISO-8601 timestamp.
`amount_usd`	Yes	The amount in USD. The settlement rail converts it to the exact atomic amount.
`submitted_at`	Yes	The submitted at this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ts`	No	The `ts` field of the response.
`note`	No	A note on how the answer was produced.
`rail`	No	The `rail` field of the response.
`basis`	No	The `basis` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sample`	No	The `sample` field of the response.
`sha256`	No	The `sha256` field of the response.
`network`	No	The `network` field of the response.
`reasons`	No	The `reasons` field of the response.
`verdict`	Yes	The decision this tool returned.
`deadline`	No	The `deadline` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`amount_usd`	No	The amount the operation concerned.
`instrument`	No	The `instrument` field of the response.
`public_key`	No	The `public_key` field of the response.
`measured_at`	No	The `measured_at` field of the response.
`p50_seconds`	No	The `p50_seconds` field of the response.
`p95_seconds`	No	The `p95_seconds` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`received_usd`	No	The `received_usd` field of the response.
`submitted_at`	No	The `submitted_at` field of the response.
`amount_atomic`	No	The `amount_atomic` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`slack_seconds`	No	The `slack_seconds` field of the response.
`profileVersion`	No	Version of the answer profile.
`settle_seconds`	No	The `settle_seconds` field of the response.
`_time_dependent`	No	The `_time_dependent` field of the response.
`expected_settlement_seconds`	No	The `expected_settlement_seconds` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 31, 2026

addedOutput schema / properties / _time_dependent

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

Added value: +{
+  "description": "The amount the operation concerned.",
+  "type": "number"
+}

addedOutput schema / properties / basis

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

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / expected_settlement_seconds

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / measured_at

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

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

addedOutput schema / properties / p95_seconds

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

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

addedOutput schema / properties / reasons

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

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

addedOutput schema / properties / slack_seconds

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

removedOutput schema / properties / status

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

addedOutput schema / properties / submitted_at

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

addedOutput schema / properties / ts

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

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

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior4/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 genuinely useful context beyond that: the response is a 29-field object including `_time_dependent` and `algorithm`, and the call costs $0.05 USDC — cost information an agent cannot get from annotations or schema.

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 question, but it is written as three stitched-together fragments separated by semicolons, with redundancy in 'for payment deadline, not conditional payment.' The middle clause costs reading effort without adding clarity.

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?

An output schema exists, so return values need not be enumerated, yet the description still hints at output shape (29 fields, `_time_dependent`, `algorithm`) and discloses pricing. For a read-only query tool with full schema coverage, that is close to sufficient; only the parameter semantics are thin.

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. However, several schema descriptions are boilerplate ('See the schema for its type and whether it is required'), and the description adds nothing about `rail`, `network`, `submitted_at`, or `deadline`, so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states its purpose as a question ('Will this payment settle inside my deadline?') rather than a verb+resource, which conveys the concept (settlement-feasibility check) but leaves the agent to infer the actual operation. The sibling exclusion for `settle_conditional_payment` helps disambiguate, but the phrasing is fragmentary and the word 'deadline' is used both as the tool's subject and as a contrast term, muddying the signal.

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 an alternative and a condition: use this rather than `settle_conditional_payment` when you want a payment deadline answer, not a conditional payment. That is real routing guidance, though the sentence is grammatically tangled and never says when this tool should not be used at all.

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.