Reputation History
by api.limitguard.ai in Security & trust
Historical reputation trend data. Returns the trust score timeline with the decay applied at each point and an overall trend.
https://api.limitguard.ai/v1/reputation/history/:entity_hash- Price
- $0.11
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 37 min ago, next in 28 min
Reliability
Latest check failed 37 min ago: Expected HTTP 402, got 400
How to call it
GET https://api.limitguard.ai/v1/reputation/history/:entity_hash
Each call costs $0.11 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
Built from the input schema. Replace the values with your own.
GET https://api.limitguard.ai/v1/reputation/history/:entity_hashExample response
The provider's example. We can't check it without paying.
{
"history": [
{
"date": "2026-01-15",
"score": 85
},
{
"date": "2026-02-15",
"score": 92
}
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.11.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.limitguard.ai/v1/reputation/history/:entity_hash'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.limitguard.ai/v1/reputation/history/:entity_hash' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.11 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.11" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.11 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.limitguard.ai%2Fv1%2Freputation%2Fhistory%2F%3Aentity_hash
const res = await pay("https://api.limitguard.ai/v1/reputation/history/:entity_hash");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.11 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.11"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.limitguard.ai/v1/reputation/history/:entity_hash")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 37 min ago | Expected HTTP 402, got 400 | 400 | 205 ms | - |
| 5 h ago | Expected HTTP 402, got 400 | 400 | 308 ms | - |
| 10 h ago | Expected HTTP 402, got 400 | 400 | 225 ms | - |
| 15 h ago | Expected HTTP 402, got 400 | 400 | 174 ms | - |
| 20 h ago | Expected HTTP 402, got 400 | 400 | 223 ms | - |
Show 10 older checks
| 24 h ago | Expected HTTP 402, got 400 | 400 | 188 ms | - |
| 29 h ago | Expected HTTP 402, got 400 | 400 | 210 ms | - |
| 34 h ago | Expected HTTP 402, got 400 | 400 | 200 ms | - |
| 38 h ago | Expected HTTP 402, got 400 | 400 | 268 ms | - |
| 43 h ago | Expected HTTP 402, got 400 | 400 | 179 ms | - |
| 47 h ago | Expected HTTP 402, got 400 | 400 | 1.3 s | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 224 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 189 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 276 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 1.1 s | - |