Comply Ai Act
by CompliancePulse in Company & people data
EU AI Act applicability check: risk classification (prohibited / Annex III high-risk / transparency / minimal + GPAI), obligations for your role (provider/deployer/importer/distributor), penalties, and the CURRENT state of the August 2026 high-risk deadline vs the Digital Omnibus deferral to December 2027 (tracked to Official Journal status). Deterministic classification with cited articles; applies to any company whose AI reaches people in the EU.
https://compliancepulse.theaslangroupllc.com/api/comply/ai-act- Price
- $0.25
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 4 h ago, next any minute now
Reliability
Latest check failed 4 h ago: Amount "0.25" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://compliancepulse.theaslangroupllc.com/api/comply/ai-act
Each call costs $0.25 in USDC on Polygon, 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://compliancepulse.theaslangroupllc.com/api/comply/ai-act?use_case=resume+screening+for+hiringParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
gpai | string | No | true if you build/fine-tune a general-purpose model itself |
lang | string | No | lang |
role | string | No | provider | deployer | importer | distributor (default deployer) |
use_case | string | Yes | What the AI system does, in plain language — e.g. "resume screening for hiring decisions" |
Example response
The listing has no example response.
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.25.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://compliancepulse.theaslangroupllc.com/api/comply/ai-act?use_case=resume+screening+for+hiring'
# 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://compliancepulse.theaslangroupllc.com/api/comply/ai-act?use_case=resume+screening+for+hiring' \
| 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.25 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.25" });
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.25 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcompliancepulse.theaslangroupllc.com%2Fapi%2Fcomply%2Fai-act
const res = await pay("https://compliancepulse.theaslangroupllc.com/api/comply/ai-act?use_case=resume+screening+for+hiring");
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.25 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.25"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://compliancepulse.theaslangroupllc.com/api/comply/ai-act?use_case=resume+screening+for+hiring")
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 |
|---|---|---|---|---|
| 4 h ago | Amount "0.25" is not in atomic token units | 402 | 260 ms | $0.25 |
| 12 h ago | Amount "0.25" is not in atomic token units | 402 | 258 ms | $0.25 |
| 21 h ago | Amount "0.25" is not in atomic token units | 402 | 257 ms | $0.25 |
| 29 h ago | Amount "0.25" is not in atomic token units | 402 | 242 ms | $0.25 |
| 37 h ago | Amount "0.25" is not in atomic token units | 402 | 265 ms | $0.25 |
Show 10 older checks
| 45 h ago | Amount "0.25" is not in atomic token units | 402 | 323 ms | $0.25 |
| 2 days ago | Amount "0.25" is not in atomic token units | 402 | 256 ms | $0.25 |
| 3 days ago | Amount "0.25" is not in atomic token units | 402 | 280 ms | $0.25 |
| 3 days ago | Amount "0.25" is not in atomic token units | 402 | 299 ms | $0.25 |
| 3 days ago | Amount "0.25" is not in atomic token units | 402 | 231 ms | $0.25 |
| 3 days ago | Amount "0.25" is not in atomic token units | 402 | 317 ms | $0.25 |
| 4 days ago | Amount "0.25" is not in atomic token units | 402 | 241 ms | $0.25 |
| 4 days ago | Amount "0.25" is not in atomic token units | 402 | 245 ms | $0.25 |
| 4 days ago | Amount "0.25" is not in atomic token units | 402 | 281 ms | $0.25 |
| 5 days ago | Amount "0.25" is not in atomic token units | 402 | 254 ms | $0.25 |