Install Jentic One Beta

Connect the AI Law Tracker Public Laws API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Law Tracker Public Laws API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fai-law-tracker.com%2Fai-law-tracker" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fai-law-tracker.com%2Fai-law-tracker" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AI Law Tracker Public Laws API.

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

GET STARTED

Start building with AI Law Tracker Public Laws API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AI Law Tracker Public Laws API for, with concrete tasks.

★ 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.

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.

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.

Submit a company profile to POST /assess and return the applicable obligations with their penalties from GET /penalties

Key Endpoints

52 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using AI Law Tracker Public Laws API through Jentic.

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.

AI Law Tracker Public Laws API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityComplianceapiKey, bearer52 EndpointsREST

For 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.

Use for: List AI-regulation records for a jurisdiction, Get the full change history for one legal record, Read the EU AI Act provisions for an article, Check which AI-law compliance deadlines are coming up

Not supported: Does not provide legal advice, file paperwork, or represent you. Use for reading AI-regulation records, obligations, deadlines, and enforcement data only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AI Law Tracker Public Laws API to your agent

Capabilities

Start building with AI Law Tracker Public Laws API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AI Law Tracker Public Laws API

Jentic AI Readiness Score

AI Law Tracker — Public Laws API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness