# LimitGuard Reputation History

> LimitGuard Reputation History is a paid API for AI agents from api.limitguard.ai, paid per call via x402, $0.11/call, status unknown (last checked 2026-10-24).

Returns the historical trust score timeline for an entity, showing how reputation has changed over time with temporal decay applied at each data point and an overall trend indicator.

## Facts

- Endpoint: GET https://api.limitguard.ai/v1/reputation/history/:entity_hash?utm_source=zero.xyz
- Price: $0.11/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/limitguard-reputation-history-c52ad628
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZAz-zSBGceIgpGIjKYdmf

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 limitguard-reputation-history-c52ad628
```

Example prompt: Can you pull the full reputation history for entity hash 'abc123xyz' from LimitGuard and tell me whether their trust score has been trending up or down over time, including how the temporal decay affects each point?

## When to prefer this

Use this endpoint when you need to understand how an entity's reputation has evolved over time rather than just its current score. It is the right choice for due diligence audits, periodic compliance reporting, or any scenario where trend direction matters as much as the current trust score. Prefer it over the quick risk score endpoint when historical context and decay-applied timelines are required.

## Known failure modes

- Unknown or unrecognized entity_hash returns a 404 or empty timeline
- Entity with no historical data returns a minimal or single-point response
- Insufficient USDC balance in agent wallet causes payment failure via x402
- Malformed entity_hash format returns a 400 validation error
- Very new entities may have too short a history to produce a meaningful trend

## How this service works

Historical reputation trend data. Returns the trust score timeline with the decay applied at each point and an overall trend.

## Output

An ordered timeline of trust scores for the given entity, where each data point reflects the decay-adjusted score at that moment in time. Also includes an overall trend indicator (e.g. improving, declining, stable) summarizing the trajectory across the full history window.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/limitguard-reputation-history-c52ad628/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.limitguard.ai](https://www.zero.xyz/host/api.limitguard.ai/llms.txt)