Install Jentic One Beta

Connect the Regbase API (v1) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Regbase API (v1), 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%2Fregbase.com%2Fregbase" | 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%2Fregbase.com%2Fregbase" | 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 Regbase API (v1) API.

Search regulatory entities with a GFFS query such as jurisdiction:US.CA "clean energy" via GET /v1/search, blending full-text and semantic vector ranking

List canonical entities filtered by type, jurisdiction, authority, status, or displayDate with GET /v1/entities and cursor paging

Follow changes to tracked entities through GET /v1/entities/changes, reading changeType, changedKeys, mergedInto, and recordedAt

Read a single entity by id, with merged entities followed to the surviving canonical id

GET STARTED

Start building with Regbase API (v1) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Regbase API (v1) API for, with concrete tasks.

★ Regulatory research agent through Jentic

A compliance analyst's agent answers questions like 'what new clean energy rules apply in California' without a developer wiring JSON:API paging and the GFFS query syntax by hand. Through Jentic the agent searches for 'search legislation by jurisdiction', loads GET /v1/search, and sends q with a jurisdiction qualifier plus free text. It then reads each hit with GET /v1/entities/{id} and downloads the source rendition so its answer cites the actual document.

Call GET /v1/search with q 'jurisdiction:US.CA "clean energy"', take the top three entity ids, read each with GET /v1/entities/{id}, and download a text rendition for the first

Change monitoring for tracked regulations

Compliance teams need to know when a rule they depend on moves. GET /v1/entities/changes returns entity-change resources with changeType, changedKeys, mergedInto, and recordedAt, filtered by GFFS on the post-change snapshot such as a jurisdiction or authority. The meta.cursor advances even when a filtered page is empty, so a scheduled poller resumes where it stopped without rescanning.

Poll GET /v1/entities/changes with filter 'jurisdiction:US.NY' and page[after] set to the stored cursor, then report each change's changeType and changedKeys

Source document retrieval

Summaries need the primary text behind them. Entity responses include texts with Public Text IDs and renditions, and GET /v1/entities/{id}/renditions/{renditionId}.{extension} returns the raw bytes with a Content-Type matching the rendition's mime, such as application/pdf, text/html, or text/plain.

Read GET /v1/entities/{id}, pick the rendition whose mime is text/plain, and download it from GET /v1/entities/{id}/renditions/{renditionId}.{extension}

Key Endpoints

5 endpoints — the regbase api serves a warehouse of regulatory entities, with resource types such as legislation and person, along with a change feed that records updates to them.

METHOD

PATH

DESCRIPTION

GET

/v1/search

Search entities with GFFS and hybrid ranking

GET

/v1/entities

List canonical entities

GET

/v1/entities/{id}

Get an entity by id

GET

/v1/entities/changes

List entity changes

GET

/v1/entities/{id}/renditions/{renditionId}.{extension}

Download a document rendition

GET

/v1/search

Search entities with GFFS and hybrid ranking

GET

/v1/entities

List canonical entities

GET

/v1/entities/{id}

Get an entity by id

GET

/v1/entities/changes

List entity changes

GET

/v1/entities/{id}/renditions/{renditionId}.{extension}

Download a document rendition

Why Jentic?

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

Setup

Wiring Regbase by hand means sending the organization key as a bearer token, parsing JSON:API resources, writing GFFS queries, and tracking meta.cursor across pages of the change feed. Through Jentic you install once, import Regbase from the API Directory, store the key once, and your agent calls it.

Permission scoping

Regbase is read-only and puts the entity id in the URL path (/v1/entities/{id}), so a rule can pin your agent to one entity, its renditions, and the operations you pick. You choose the operations it may call, so broader reads like full search or bulk listing are not included unless you add them.

Credential isolation

Your Regbase API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search legislation by jurisdiction' or 'list regulation changes', and Jentic returns the matching Regbase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Regbase API (v1) API through Jentic.

What authentication does the Regbase API use?

Per its OpenAPI spec, the Regbase API uses an organization API key sent as a bearer token in the Authorization header, in the form Authorization: Bearer rb_live_ followed by the key. Keys are created in your Regbase account settings. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

Which fields can I filter on with the Regbase API?

GFFS filters and returned attributes are limited to type, title, name, displayDate, jurisdiction, localIdentifier, localType, authority, and status. Operators include equality and multi-value OR, ~ for contains, comparisons, .. ranges, and leading - for negation. On the change feed, change metadata such as changeType and recordedAt is not filterable.

What are the rate limits for the Regbase API?

The OpenAPI spec does not specify rate limits; it caps page size at 100 results per page. Check the Regbase documentation at https://regbase.com and your account settings for current limits.

Is there a Regbase MCP server?

You don't need an MCP server to give your agent Regbase. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the search and change-feed operations it needs, discovered on demand rather than loaded into its context up front.

How do I search legislation by jurisdiction through Jentic?

Search Jentic for 'search legislation by jurisdiction', load GET /v1/search, and pass q as a GFFS query such as jurisdiction:US.CA "clean energy". Qualifiers filter first and the remaining text is ranked with full-text and semantic vector search. 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 Regbase API?

Yes. For a monitoring job, write a rule that allows only the entity change feed and single-entity reads, and the agent can watch for updates and look up what changed but cannot run open-ended searches or bulk-download renditions. Every call it makes is logged.

Regbase API (v1)

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityCompliancebearer5 EndpointsREST

For Agents

Search and list legislation and other regulatory entities by jurisdiction, authority, and status, follow the entity change feed, and download the source document renditions.

Use for: Find California legislation about clean energy, Monitor changes to bills in my jurisdiction since yesterday, List all enacted regulations from a given authority, Get the full record for a Regbase entity id

Not supported: Does not file regulatory submissions, give legal advice, or edit legislative records. Use for searching and monitoring regulatory entities and downloading their source documents only.

The Regbase API serves a warehouse of regulatory entities, with resource types such as legislation and person, along with a change feed that records updates to them. Entities can be listed or searched with GFFS qualifiers on fields like jurisdiction, authority, status, and displayDate, and free-text search ranks the remaining terms with a fusion of full-text and semantic vector search. Each entity carries Public Text IDs with downloadable renditions, so the source document can be fetched as PDF, HTML, or plain text. Responses follow JSON:API, and merged entities resolve to their surviving canonical id.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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

29%

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.

45%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Regbase API (v1) to your agent

Capabilities

Start building with Regbase API (v1) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Regbase API (v1)

Jentic AI Readiness Score

Regbase API (v1)

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