Synthex Forge — x402 Paid Agent Services

Get Bureau Preflight

get_bureau_preflight

Read-onlyIdempotent

Inspect ANY x402 endpoint: reachable?. use it rather than check_bureau_receipt for bureau preflight, not bureau receipt; an object with 27 fields including algorithm, blocked.

Input Schema

Name	Required	Description	Default
`url`	Yes	Must not be empty. The handler rejects an empty value with 400 `bad_request`.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`ts`	No	The `ts` field of the response.
`note`	No	A note on how the answer was produced.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`target`	No	The `target` field of the response.
`blocked`	No	The `blocked` field of the response.
`network`	No	The `network` 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.
`instrument`	No	The `instrument` field of the response.
`public_key`	No	The `public_key` field of the response.
`recognised`	No	The `recognised` field of the response.
`supersedes`	No	The `supersedes` field of the response.
`finding_ids`	No	The `finding_ids` field of the response.
`observed_at`	No	The `observed_at` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`report_sha256`	No	The `report_sha256` field of the response.
`signature_alg`	No	The `signature_alg` field of the response.
`standard_version`	No	The `standard_version` field of the response.
`network_recognised`	No	The `network_recognised` field of the response.
`network_verifiable`	No	The `network_verifiable` field of the response.
`independently_verifiable`	No	The `independently_verifiable` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / blocked

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

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

addedOutput schema / properties / evidence

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

addedOutput schema / properties / finding_ids

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

addedOutput schema / properties / id

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

addedOutput schema / properties / independently_verifiable

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / network

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

addedOutput schema / properties / network_recognised

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

addedOutput schema / properties / network_verifiable

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

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

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

addedOutput schema / properties / report_sha256

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

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

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

removedOutput schema / properties / status

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

addedOutput schema / properties / supersedes

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

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

B3.4/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 the behavioral payoff beyond that: it performs a reachability probe and returns a 27-field object including `algorithm` and `blocked`, which tells the agent what evidence it gets back. It does not mention failure modes (unreachable endpoint, timeout) or cost/payment implications of probing an x402 endpoint.

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 not front-loaded or clean: "reachable?." is a fragment with stray punctuation and the sibling instruction is restated twice ("rather than check_bureau_receipt for bureau preflight, not bureau receipt"). The return-object detail is tacked on with a semicolon rather than integrated.

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 and annotations cover safety, so those burdens are lifted. Still, for a one-parameter probe of an arbitrary endpoint, the agent is left without the domain meaning of "bureau preflight", whether payment or authentication is required to reach the endpoint, or what a failed/unreachable result looks like.

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% and the single `url` parameter is documented there with its empty-value/400 constraint. The description adds nothing about the URL parameter — no format, scheme, or whether the target must be a paying x402 resource — so the baseline 3 applies.

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?

"Inspect ANY x402 endpoint: reachable?" gives a verb and a resource and hints at a reachability check, but the core concept — what a "bureau preflight" actually is and how it differs from a receipt check — is never defined. The trailing "an object with 27 fields including algorithm, blocked" adds some concreteness but reads as an unstructured fragment rather than a statement of purpose.

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 an explicit alternative and a selection condition: use this rather than `check_bureau_receipt` for preflight, not for receipt inspection. That is a real routing signal an agent can act on. It stops short of stating prerequisites or when neither tool applies, and the phrasing "for bureau preflight, not bureau receipt" is circular.

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.