canonical: https://jentic.com/apis/ai-law-tracker.com/ai-law-tracker # AI Law Tracker Public Laws API The AI Law Tracker API is a read-only JSON interface over an audited dataset of AI regulation across US states, US federal, the EU, and other jurisdictions. It lists and filters legal records, returns a record's full change history, and serves EU AI Act provisions by article, paragraph, recital, and annex. Derived views cover obligations, penalties, upcoming compliance deadlines, enforcement actions, and litigation matters. A company profile can be assessed for applicable obligations and a risk score, and the data is informational rather than legal advice. ## For AI agents Read AI-regulation records, EU AI Act provisions, obligations, penalties, deadlines, and enforcement actions for AI agents, and assess a company profile for a risk score. ## Scope Does not provide legal advice, file paperwork, or represent you. Use for reading AI-regulation records, obligations, deadlines, and enforcement data only. ## Capabilities - List and filter AI-regulation records and read one record's full change history - Read EU AI Act provisions by article, paragraph, recital, or annex - Poll a unified changelog for what changed since a given point - Derive AI-law obligations and penalties for a jurisdiction, sector, or use - Assess a company profile for applicable obligations and a risk score - Browse AI enforcement actions and litigation matters ## Use cases ### AI compliance research agent An AI agent answering compliance questions needs grounded, sourced regulation rather than a model's recollection. Through Jentic the agent searches for 'read the obligations for a sector', loads the matching AI Law Tracker operation with its input schema, and reads obligations and penalties for the jurisdiction with any key injected at call time. Every record links to a primary source so the agent can cite it. Example prompt: Read GET /obligations for a jurisdiction and sector, then fetch GET `/laws/{id}` for each cited record ### Regulatory change monitoring A compliance team wants to know what moved in AI law since their last check. AI Law Tracker exposes a unified changelog and a per-record change history, so a monitor can poll for changes since a timestamp and open the affected records. Upcoming compliance deadlines are available as JSON or iCal for calendaring. Example prompt: Poll GET /changes for updates since a timestamp and list the affected records with their deadlines from GET /deadlines ### Company obligation assessment A team scoping their exposure submits a company profile and gets back the obligations that apply plus a risk score. AI Law Tracker accepts the profile and returns applicable obligations and a one-to-ten risk score, grounded in the underlying records. An agent can run the assessment and attach the obligations and their penalties for review. Example prompt: Submit a company profile to POST /assess and return the applicable obligations with their penalties from GET /penalties ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/laws` | List and filter legal records | | GET | `/laws/{id}` | Get one record by id | | GET | `/eu-ai-act-provisions` | List EU AI Act provisions | | GET | `/changes` | Unified changelog of record changes | | GET | `/deadlines` | Upcoming AI-law compliance deadlines | | GET | `/obligations` | Derived AI-law obligations | | POST | `/assess` | Assess a company profile for obligations and a risk score | | GET | `/enforcement` | AI enforcement actions and litigation | ## Key resources - **Legal records** — List, filter, read, and track the change history of AI-regulation records - **EU AI Act** — Provisions by article, paragraph, recital, and annex - **Compliance views** — Obligations, penalties, deadlines, and the company-profile assessment - **Enforcement** — AI enforcement actions and litigation matters with their chains ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 64 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 93 / 100 - Security: 55 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/ai-law-tracker.com/ai-law-tracker/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring AI Law Tracker by hand means deciding which endpoints need a key, obtaining one by email, and sending it as either an X-API-Key header or a bearer token depending on the call. Through Jentic you install once, import AI Law Tracker from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The data lives under read paths such as `/laws/{id}` and /obligations, so a rule can pin your agent to the read operations it needs. You choose which it may call, so write operations like issuing a key, creating a webhook, or deleting the account are not included unless you add them. - **Credential handling:** Your AI Law Tracker key is stored once, encrypted, by your own Jentic One instance and attached as the X-API-Key or bearer header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read the obligations for a sector' or 'check upcoming AI-law deadlines', and Jentic returns the matching AI Law Tracker operation with its input schema so the agent calls the right endpoint. ## Related APIs - **Open States API** — US state legislatures, bills, and legislators that pair with AI-specific regulation records - **Regulations.gov API** — US federal rulemaking dockets and public comments across all agencies ## FAQ ### What authentication does the AI Law Tracker API use? Per its OpenAPI spec, many endpoints are open and need no credential, while a key raises your tier and limits. The key is sent either as an X-API-Key header or as a bearer token in the Authorization header, and POST `/auth/token` or POST /keys issues one by email. Through Jentic any key is held by your own instance and attached per call. ### Can I read the EU AI Act provisions with the AI Law Tracker API? Yes. GET /eu-ai-act-provisions returns the provision text by article, paragraph, recital, and annex. For other records, GET /laws lists and filters legal records and GET `/laws/{id}` returns a single record with links to its primary sources. ### What are the rate limits for the AI Law Tracker API? Rate limits depend on the tier tied to your key rather than a single fixed ceiling in the spec, and GET /me reports your tier, limits, and live usage once you hold a key. Check the AI Law Tracker documentation for the per-tier allowance before polling the changelog frequently. ### Is there an AI Law Tracker MCP server? You do not need an MCP server to give your agent AI Law Tracker. Jentic connects it directly from the API Directory: import it, store any key once, and your agent calls the records, obligations, and enforcement operations it needs. ### How do I assess a company's AI-law obligations through Jentic? Search Jentic for 'assess a company profile for AI-law obligations', load the POST /assess operation, and submit the profile. It returns the applicable obligations and a risk score, and the data is informational rather than legal advice. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the AI Law Tracker API? Yes. The dataset is mostly read-only, so a rule can allow the agent just the lookups a task needs, such as listing laws and reading obligations, while leaving key issuance, webhook creation, and account deletion out of reach. The agent stays bound to the operations you grant, and every call is logged.