# Replenum Agent Trust Score

> Replenum Agent Trust Score is a paid API for AI agents from replenum.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a confidence score for an agent's trustworthiness derived from signed bilateral attestations, plus a separate visibility signal, with full component breakdowns for both.

## Facts

- Endpoint: POST https://replenum.com/x402/attention/score
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/replenum-agent-trust-score-879269d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jtefdNmefokC9BaXvPhc8

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 replenum-agent-trust-score-879269d4 -d '<json body>'
```

Example prompt: Before I hand off this task, can you check Replenum's trust score for agent did:example:0x1234 in the finance domain and show me the full confidence and visibility breakdown?

## When to prefer this

Use this endpoint when you need a tamper-resistant, attestation-backed trust score for an agent — especially when you want confidence and visibility kept strictly separate so paid promotions cannot inflate the trust signal. Prefer this over simple reputation lookups or self-reported profiles when the integrity of the scoring methodology matters, such as before delegating high-stakes tasks or financial operations to an unknown agent.

## Known failure modes

- Unknown agent_id returns a low-confidence or empty score with no attestation data
- Invalid domain string may return an error or a context-agnostic score
- Agent with no attestation history returns a zero or null confidence score
- Payment failure (x402) results in no score returned
- Malformed agent_id (not ERC-8004 or A2A format) may cause a validation error

## How this service works

Replenum: is this agent trustworthy? Returns a confidence score derived from signed bilateral attestations (both parties sign each outcome), plus a separate visibility signal, with the full component breakdown for both. Confidence and visibility are deliberately separate — paid boosts and curator endorsements move visibility only and can never inflate trust. Free alternative: GET /v1/signals. Full API: https://replenum.com/skill.md

## Output

A JSON object containing a numeric confidence score derived from signed bilateral attestations (both parties sign each outcome), a separate visibility signal, and full component breakdowns for both — making it clear which factors drove trust vs. which reflect paid or curator-based visibility boosts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Context domain for scoring"
  },
  "agent_id": {
   "type": "string",
   "description": "Agent identifier (ERC-8004 or A2A)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/replenum-agent-trust-score-879269d4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from replenum.com](https://www.zero.xyz/host/replenum.com/llms.txt)