78trust / 100
Reports Entity
by api.limitguard.ai in Security & trust
x402 APIPassing, checked 7 min ago
Per-entity report built from one real check's signals: identity, sanctions and PEP screening, domain signals, trust score (risk.trust_score, 0-100, 100 = best), correlations with the caller's earlier reports, sources and an evidence hash. A source that did not answer is shown unavailable, never clean.
POST https://api.limitguard.ai/v1/reports/entity
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 100%
- Response time
- 198 ms typical, 248 ms slowest 5%
- Last check
- 7 min ago
- Next check
- in 21 min
How to call it
# See the payment challenge (nothing is charged)
curl -i -X POST "https://api.limitguard.ai/v1/reports/entity" \
-H "content-type: application/json" \
-d '{}'import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.limitguard.ai%2Fv1%2Freports%2Fentity
const res = await pay("https://api.limitguard.ai/v1/reports/entity", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({}),
});
console.log(await res.json());Example input
{}Example output
{
"check_id": "3f9c1e2a-1111-4a2b-9c3d-000000000000",
"correlations": {
"links": [],
"scope_note": "workspace_reports",
"status": "ok"
},
"created_at": "2026-09-24T10:00:00Z",
"domain": {
"domain": "acme.example",
"domain_age_days": 3200,
"status": "ok"
},
"entity": {
"country": "NL",
"entity_name": "Acme Corp BV"
},
"evidence": {
"hash_algorithm": "sha256",
"report_hash": "sha256:..."
},
"pep": {
"exposure": false,
"matches": [],
"status": "ok"
},
"report_id": "3f9c1e2a-1111-4a2b-9c3d-000000000001",
"risk": {
"cluster": "verified",
"confidence": 0.9,
"recommendation": "APPROVE",
"sources_checked": 5,
"trust_level": "high",
"trust_score": 87
},
"sanctions": {
"lists": [],
"result": "no_match",
"status": "ok",
"threshold": 0.7
},
"sources": [
{
"source": "opensanctions",
"status": "ok"
}
]
}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 |
|---|---|---|---|---|
| 7 min ago | Passed | 402 | 115 ms | $1.85 |
| 4 h ago | Passed | 402 | 248 ms | $1.85 |
| 7 h ago | Passed | 402 | 160 ms | $1.85 |
| 11 h ago | Passed | 402 | 220 ms | $1.85 |
| 14 h ago | Passed | 402 | 177 ms | $1.85 |
| 18 h ago | Passed | 402 | 196 ms | $1.85 |
| 22 h ago | Passed | 402 | 242 ms | $1.85 |
| 25 h ago | Passed | 402 | 198 ms | $1.85 |
| 29 h ago | Passed | 402 | 208 ms | $1.85 |
| 32 h ago | Passed | 402 | 210 ms | $1.85 |
| 37 h ago | Passed | 402 | 69 ms | $1.85 |
| 40 h ago | Passed | 402 | 64 ms | $1.85 |
| 43 h ago | Passed | 402 | 436 ms | $1.85 |