Back to Browse
LimitGuard Reputation History
x402
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-10).
Retrieves the historical trust score timeline for a given entity (AI agent, business, or wallet) by its entity hash
Price / call$0.11
Success—
StatusUnknown
How this service works
Check every lead against official business registers, VAT and sanctions lists. Proceed, review or block, with the source. 5 lead checks free.
Output
Returns a chronological array of date-and-score pairs representing the entity's trust score at each recorded point in time (e.g. [{date: '2026-01-15', score: 85}, {date: '2026-02-15', score: 92}]), allowing trend analysis and historical auditing of reputation.
Example use cases
Due diligence before agent partnership
“Before we integrate with that third-party AI agent, can you check their trust score history on LimitGuard using entity hash 'agt_7f3d9a' and show me how their reputation has trended over the last six months?”
Auditing a business counterparty's trust trend
“I need to review the reputation history for the business with entity hash 'biz_44c2e1' — can you fetch all their historical trust scores from LimitGuard so I can see if there were any drops or red flags?”
Monitoring own agent's reputation over time
“Can you pull the LimitGuard reputation history for our own agent using entity hash 'myagent_99b12f' so I can verify that our trust scores have been consistently high and spot any anomalies?”
Technical details
Endpoint
GEThttps://api.limitguard.ai/v1/reputation/history/%7Bid%7D?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need historical reputation trend data for an entity rather than just its current score — ideal for due diligence workflows, counterparty risk auditing, monitoring reputation drift over time, or detecting sudden trust score drops that may indicate newly flagged risk. Prefer this over a point-in-time score endpoint when longitudinal analysis or compliance documentation is required.
Side effects
- Invalid or unknown entity_hash returns empty history or 404 error
- Malformed entity_hash format causes request validation failure
- Insufficient prepaid balance results in 402 Payment Required response
- Entity with no history yet returns empty history array
- Rate limiting or quota exceeded returns 429 error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| note | string | |
| inputrequired | object | |
| output | object | |
| sandbox | object | |
| recovery | object | |
| prepaidBalance | object | |
| documentation_url | string | |
| cachedTierAvailable | boolean |
Output
Schema · Response
{
"type": "json",
"example": {
"history": [
{
"date": "2026-01-15",
"score": 85
},
{
"date": "2026-02-15",
"score": 92
}
]
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"