# Synthex Forge Agent Reputation Trusted Route Ranker

> Synthex Forge Agent Reputation Trusted Route Ranker is a paid API for AI agents from x402.synthexforge.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-23).

Ranks and scores candidate counterparty routes by agent reputation using historical outcome events (success, fail, dispute)

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/agent-reputation/trusted-route?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthex-forge-agent-reputation-trusted-route-ranker-f164c833
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lV5cUVs6c-juoWnqlgiCa

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability synthex-forge-agent-reputation-trusted-route-ranker-f164c833 -d '<json body>'
```

Example prompt: Before I send payments to these three routes — agent-A, agent-B, and agent-C — can you rank them by reputation using their past outcome history: agent-A had 5 successes and 1 dispute, agent-B had 3 successes and 0 disputes, agent-C had 2 successes and 2 failures?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically rank or select among multiple counterparty routes based on historical outcome data before executing a payment or delegating a task. Particularly valuable in multi-agent systems where trust and reputation are critical for route selection, and when you have structured event histories (successes, failures, disputes) for each candidate. Prefer this over generic scoring services when you need Ed25519-attested, cryptographically signed reputation assessments on Base mainnet.

## Known failure modes

- Missing or malformed routes array returns validation error
- Empty events arrays may result in unscored or equally ranked routes
- Invalid outcome enum values (not success/fail/dispute) may cause rejection
- Payment not attached or insufficient USDC triggers HTTP 402 payment-required response
- Malformed agent/route identifiers may cause lookup failures
- Network timeout if route list is very large

## How this service works

Synthex Forge x402 Receive: 41 paid verification, attestation and governance endpoints (Ed25519 + SHA-256 signed artifacts) plus free verify/public-key/standard sibling routes. Paid routes answer HTTP 402 with an x402 v2 `payment-required` envelope (atomic USDC on Base mainnet, chain ID 8453). Free routes are declared with `security: []` per the x402scan discovery spec.

## Output

Returns a JSON response indicating success (ok: true) along with ranked reputation scores for the submitted candidate routes, ordered by trustworthiness based on the outcome event data provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "routes": {
   "type": "array",
   "description": "Candidate counterparty routes to rank: {route|id|agent, events:[{outcome: success|fail|dispute, amount_usd?, ts?, note?}]}"
  },
  "routes[]": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-agent-reputation-trusted-route-ranker-f164c833/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.synthexforge.com](https://www.zero.xyz/host/x402.synthexforge.com/llms.txt)