# Synthex Forge Agent Reputation Scoring

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

Submits signed outcome events for an agent identifier and receives a reputation assessment based on its historical success, failure, and dispute record.

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/agent-reputation?utm_source=zero.xyz
- Price: $0.25/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-scoring-0d8a0e02
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o3K0grj6DewwuBFzlgxOh

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-scoring-0d8a0e02 -d '<json body>'
```

Example prompt: Can you compute a reputation score for agent wallet 0xABC123 using these three outcome events: a successful $50 task completed yesterday, a failed $20 task last week, and a dispute for $100 two weeks ago?

## When to prefer this

Choose this endpoint when you need cryptographically attested agent reputation scoring backed by Ed25519 signatures and SHA-256 artifacts, particularly for governance workflows in multi-agent systems operating on Base mainnet. It is ideal when you need on-chain-adjacent trust signals for agent wallets or DIDs, rather than simple self-reported metrics or centralized reputation databases.

## Known failure modes

- Payment not provided or invalid — returns HTTP 402 with x402 v2 payment-required envelope specifying USDC on Base mainnet (chain ID 8453)
- Malformed agent identifier — returns error if wallet/DID/service key is not recognizable
- Invalid or unsigned outcome events — rejected if event structure does not conform to expected schema
- Missing required fields (agent or events array) — returns validation error
- Network or signing key issues on provider side — may return 5xx

## 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 object with an 'ok' boolean indicating whether the reputation computation and attestation were accepted. The full signed artifact (Ed25519 + SHA-256) reflects the aggregated outcome history for the submitted agent identifier.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent": {
   "type": "string",
   "description": "Agent identifier (wallet / DID / service key) whose outcome history is being assessed."
  },
  "events": {
   "type": "array",
   "description": "Signed outcome events: {outcome: success|fail|dispute, amount_usd?, ts?, note?}"
  },
  "events[]": {
   "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-scoring-0d8a0e02/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)