Compliance Readiness
by api.limitguard.ai in Security & trust
EU AI Act readiness self-assessment for one AI system. Send the system_type and the checklist items you have completed (completed_items); returns the EU AI Act risk level for that system type, a readiness score and the open gaps. entity_id is your label: nothing is looked up about it.
https://api.limitguard.ai/v1/compliance/readiness/:entity_id- Price
- $0.11
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Expected HTTP 402, got 400
How to call it
GET https://api.limitguard.ai/v1/compliance/readiness/:entity_id
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
From the listing.
GET https://api.limitguard.ai/v1/compliance/readiness/:entity_id?completed_items=risk_management&system_type=trust_scoringParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
completed_items | string | No | A checklist item you have completed, one parameter per item: risk_management, data_governance, technical_docs, record_keeping, transparency, human_oversight, accuracy_robustness |
system_type | string | No | AI system type: credit_scoring, trust_scoring, biometric_identification or employment_screening (others answer UNDETERMINED) |
Example response
The provider's example. We can't check it without paying.
Example response, 38 lines
{
"basis": "self_assessment",
"completed_items": 1,
"days_until_enforcement": 0,
"entity_id": "acme-ai",
"gaps": [
{
"id": "data_governance",
"requirement": "Data governance and quality (Art. 10)"
},
{
"id": "technical_docs",
"requirement": "Technical documentation (Art. 11)"
},
{
"id": "record_keeping",
"requirement": "Automatic logging/record-keeping (Art. 12)"
},
{
"id": "transparency",
"requirement": "Transparency and information to users (Art. 13)"
},
{
"id": "human_oversight",
"requirement": "Human oversight measures (Art. 14)"
},
{
"id": "accuracy_robustness",
"requirement": "Accuracy, robustness, cybersecurity (Art. 15)"
}
],
"note": "Self-assessment: the score counts the completed_items you sent against the 7 EU AI Act high-risk obligations. entity_id is your label; nothing is looked up about it.",
"readiness_score": 14,
"risk_level": "HIGH",
"system_type": "trust_scoring",
"total_items": 7,
"urgency": "critical"
}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/compliance/readiness/:entity_id?completed_items=risk_management&system_type=trust_scoring'
# 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/compliance/readiness/:entity_id?completed_items=risk_management&system_type=trust_scoring' \
| 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%2Fcompliance%2Freadiness%2F%3Aentity_id
const res = await pay("https://api.limitguard.ai/v1/compliance/readiness/:entity_id?completed_items=risk_management&system_type=trust_scoring");
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/compliance/readiness/:entity_id?completed_items=risk_management&system_type=trust_scoring")
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 |
|---|---|---|---|---|
| 3 h ago | Expected HTTP 402, got 400 | 400 | 382 ms | - |
| 7 h ago | Expected HTTP 402, got 400 | 400 | 303 ms | - |
| 12 h ago | Expected HTTP 402, got 400 | 400 | 245 ms | - |
| 17 h ago | Expected HTTP 402, got 400 | 400 | 260 ms | - |
| 22 h ago | Expected HTTP 402, got 400 | 400 | 664 ms | - |
Show 10 older checks
| 26 h ago | Expected HTTP 402, got 400 | 400 | 319 ms | - |
| 31 h ago | Expected HTTP 402, got 400 | 400 | 282 ms | - |
| 35 h ago | Expected HTTP 402, got 400 | 400 | 246 ms | - |
| 40 h ago | Expected HTTP 402, got 400 | 400 | 174 ms | - |
| 44 h ago | Expected HTTP 402, got 400 | 400 | 218 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 173 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 288 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 188 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 220 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 213 ms | - |