Synthex Forge — x402 Paid Agent Services

Check Bureau Receipt

check_bureau_receipt

Read-onlyIdempotent

x402 Bureau — conformance-check any issuer's receipt/offer. use it rather than get_bureau_preflight for bureau receipt, not bureau preflight; an object with 31 fields including algorithm, artifact_kind. $0.05 USDC.

Input Schema

Name	Required	Description	Default
`offer`	No	The offer this operation operates on. See the schema for its type and whether it is required.
`receipt`	No	The receipt to operate on.

Output Schema

Name	Required	Description
`id`	No	The `id` 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.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`checked`	No	The `checked` field of the response.
`evidence`	No	The `evidence` field of the response.
`findings`	No	The `findings` field of the response.
`severity`	No	The `severity` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`conformant`	No	The `conformant` field of the response.
`has_sha256`	No	The `has_sha256` field of the response.
`hash_valid`	No	The `hash_valid` field of the response.
`instrument`	No	The `instrument` field of the response.
`public_key`	No	The `public_key` field of the response.
`observed_at`	No	The `observed_at` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`artifact_kind`	No	The `artifact_kind` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`signature_alg`	No	The `signature_alg` field of the response.
`top_level_keys`	No	The `top_level_keys` field of the response.
`signature_valid`	No	The `signature_valid` field of the response.
`issuer_key_known`	No	The `issuer_key_known` field of the response.
`standard_version`	No	The `standard_version` field of the response.
`recomputed_sha256`	No	The `recomputed_sha256` field of the response.
`artifact_signature`	No	The `artifact_signature` field of the response.
`declared_algorithm`	No	The `declared_algorithm` field of the response.
`schema_conformance`	No	The `schema_conformance` field of the response.
`has_signature_block`	No	The `has_signature_block` field of the response.
`signature_valid_against_declared_key`	No	The `signature_valid_against_declared_key` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / artifact_kind

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

addedOutput schema / properties / artifact_signature

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

addedOutput schema / properties / checked

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

addedOutput schema / properties / conformant

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

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

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

addedOutput schema / properties / has_sha256

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

addedOutput schema / properties / has_signature_block

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

addedOutput schema / properties / hash_valid

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

addedOutput schema / properties / id

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / issuer_key_known

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

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

addedOutput schema / properties / recomputed_sha256

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

addedOutput schema / properties / schema_conformance

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

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

addedOutput schema / properties / signature_valid_against_declared_key

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

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

addedOutput schema / properties / value

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

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world, so the description does not need to restate safety traits. It adds useful behavioral context by disclosing the $0.05 USDC cost and that the result is an object with 31 fields including algorithm and artifact_kind.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and the sibling routing guidance, followed by output and cost details. It is compact, but the semicolon-separated clause about the 31-field object is slightly awkward and partially duplicates what the output schema can provide.

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?

Given the strong annotations, full schema coverage, and an output schema, the description provides enough context to select and invoke the tool. It could be more complete by saying whether both offer and receipt are expected together or what a failed conformance check means, but the structured fields fill most of that gap.

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 schema already documents both the offer and receipt parameters. The description adds only that these relate to 'any issuer's receipt/offer,' without clarifying formats, required nesting, or how the two parameters interact.

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

Purpose5/5

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

The description states a specific verb and resource: 'conformance-check any issuer's receipt/offer.' It also distinguishes itself from a sibling by saying to use it rather than `get_bureau_preflight` for bureau receipt, not bureau preflight.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative tool (`get_bureau_preflight`) and the condition that selects this tool: bureau receipt rather than bureau preflight. The routing guidance is clear enough for an agent to choose between the two without opening either schema.

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.