CF Enforcement Check
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://enforcement.cfsoft.us/v1/check
· transport HTTP+JSON
Federal Enforcement & Court Record Check enforcement-check
Any federal enforcement action, court record, or filing against this company? Query org, optionally cik and state. $0.05 USDC per call via x402 (HTTP 402, not A2A payment messages). Returns a records_found/no_records verdict, confidence, basis, counts, brief per-record matches, and aggregate stats. Not a compliance determination — a name match, not an entity resolution.
complianceenforcementcourt-recordslegalcorporateFull Enforcement Report enforcement-report
Everything in enforcement-check with full per-record detail: court, case number, case type, the official source URL and the courtpls.com page URL, plus per-month and per-case-type breakdowns in stats. $0.50 USDC per call via x402.
complianceenforcementcourt-recordslegalcorporateaudit2026-10-29 from https://enforcement.cfsoft.us/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.