Synthex Forge — x402 Paid Agent Services

Get Bureau Reputation

get_bureau_reputation

Read-onlyIdempotent

PAID ($0.10): compute a deterministic reputation. use it rather than get_bureau_reputation_corpus for bureau reputation, not bureau reputation corpus; an object with 26 fields including algorithm, breakdown. $0.1 USDC.

Input Schema

Name	Required	Description	Default
`events`	No	The events this operation operates on. See the schema for its type and whether it is required.
`subject`	Yes	The subject the operation is applied to — an id, a URL or a name, depending on the operation.

Output Schema

Name	Required	Description
`fail`	No	The `fail` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`dispute`	No	The `dispute` field of the response.
`payable`	No	The `payable` field of the response.
`subject`	No	The `subject` field of the response.
`success`	No	The `success` field of the response.
`verdict`	Yes	The decision this tool returned.
`algorithm`	No	The `algorithm` field of the response.
`breakdown`	No	The `breakdown` field of the response.
`instrument`	No	The `instrument` field of the response.
`public_key`	No	The `public_key` field of the response.
`not_payable`	No	The `not_payable` field of the response.
`observed_at`	No	The `observed_at` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`events_total`	No	The `events_total` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`signature_alg`	No	The `signature_alg` field of the response.
`signed_events`	No	The `signed_events` field of the response.
`events_excluded`	No	The `events_excluded` field of the response.
`unsigned_events`	No	The `unsigned_events` field of the response.
`standard_version`	No	The `standard_version` field of the response.
`events_classified`	No	The `events_classified` field of the response.
`reliability_score`	No	The `reliability_score` field of the response.
`volume_usd_observed`	No	The `volume_usd_observed` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / breakdown

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

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

addedOutput schema / properties / events_classified

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

addedOutput schema / properties / events_excluded

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

addedOutput schema / properties / events_total

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

addedOutput schema / properties / fail

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

addedOutput schema / properties / instrument

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

addedOutput schema / properties / not_payable

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

addedOutput schema / properties / observed_at

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

addedOutput schema / properties / payable

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

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

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

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

addedOutput schema / properties / success

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

addedOutput schema / properties / unsigned_events

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

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "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 this as read-only, idempotent, non-destructive, and closed-world. The description adds valuable context beyond that: it is a paid call ($0.10 USDC), deterministic, and returns an object with 26 fields including algorithm and breakdown.

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?

The description is short and front-loads the paid nature, but it repeats the price ($0.10 and $0.1 USDC) and contains a redundant, awkward phrase distinguishing 'bureau reputation' from 'bureau reputation corpus.'

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 existence of an output schema, full parameter schema coverage, and annotations, the description provides enough context for correct invocation: paid cost, deterministic behavior, and a rough sense of the return shape. No major gaps remain.

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 subject and events parameters. The description adds no additional parameter-level meaning, which fits the baseline 3 for high-coverage schemas.

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?

States a specific verb ('compute') and resource ('deterministic reputation') scoped to bureau reputation, and explicitly distinguishes it from the sibling get_bureau_reputation_corpus. The phrasing 'for bureau reputation, not bureau reputation corpus' is slightly awkward but still clear.

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?

Explicitly tells the agent to use this tool rather than get_bureau_reputation_corpus when the task is bureau reputation. It does not provide broader when-not-to-use guidance, but the key sibling routing decision is covered.

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.