Install Jentic One Beta

Connect the GoCodebook API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GoCodebook 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%2Fgocodebook.com%2Fgocodebook" | 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%2Fgocodebook.com%2Fgocodebook" | 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 GoCodebook API.

Search California city and county ordinances and get cited excerpts with links

Run a search by POST body or as a GET query string

List the California cities and counties the service covers

Fetch one jurisdiction and the local codes held for it

Read the topic ids reserved for state law

GET STARTED

Start building with GoCodebook API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GoCodebook API for, with concrete tasks.

★ Agent-Driven Ordinance Lookup

An AI agent answers a question about a local law and needs the actual code text, not a guess. It searches the relevant California jurisdiction, reads back verbatim excerpts with citations and links, and cites them in its answer. Jentic exposes the GoCodebook search operation with its input schema so the agent sends the query and jurisdiction correctly on the first call.

Search a named California city for its short-term rental ordinance and return the cited excerpts with their source links

Jurisdiction Coverage Checks

A tool needs to confirm whether a given California city or county is covered before it promises an answer. The GoCodebook API lists the covered jurisdictions and returns one jurisdiction with the local codes held for it, so the tool can tell a user up front what is available. Coverage is read directly rather than assumed.

List the covered jurisdictions, then fetch one county to see the local codes held for it

Cited Legal Research

A research workflow gathers ordinance text with citations for a compliance brief. The GoCodebook API returns verbatim excerpts, citations, and links for each search, with an AI overview on paid searches, so the brief quotes the code rather than paraphrasing it. Searches that return no results are not charged.

Run a paid search for a topic in one city and capture the verbatim excerpts and citations for a compliance brief

Key Endpoints

5 endpoints — the gocodebook api searches california local ordinances, the city and county codes, and returns structured results with verbatim excerpts, citations, and links.

METHOD

PATH

DESCRIPTION

POST

/v1/search

Search local ordinances

GET

/v1/search

Search local ordinances by query string

GET

/v1/jurisdictions

List covered California cities and counties

GET

/v1/jurisdictions/{id}

Fetch one jurisdiction and its local codes

GET

/v1/topics

Read topic ids reserved for state law

POST

/v1/search

Search local ordinances

GET

/v1/search

Search local ordinances by query string

GET

/v1/jurisdictions

List covered California cities and counties

GET

/v1/jurisdictions/{id}

Fetch one jurisdiction and its local codes

GET

/v1/topics

Read topic ids reserved for state law

Why Jentic?

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

Setup

Wiring the GoCodebook API by hand means managing its gcb_live_ bearer token, deciding between the keyless free sample and paid searches, and handling the POST and GET search forms. Through Jentic you install once, import GoCodebook from the API Directory, store the token once, and your agent calls it.

Permission scoping

GoCodebook's search takes the query in the request body or query string, so a rule bounds which operations your agent may call, such as search and jurisdiction lookups. Every operation is a read, so you choose exactly which lookups the agent may run and nothing it calls changes data.

Credential isolation

Your GoCodebook token 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 a local ordinance' or 'list covered jurisdictions', and Jentic returns the matching GoCodebook operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using GoCodebook API through Jentic.

What authentication does the GoCodebook API use?

The GoCodebook API accepts a bearer token in the Authorization header, in the gcb_live_ key format, for paid access, while a keyless free sample is available at a per-address rate limit per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in your agent's prompt or logs.

Can I search local ordinances with the GoCodebook API?

Yes. The search operation takes a query and a jurisdiction, by POST body or GET query string, and returns verbatim excerpts with citations and links. Paid searches add an AI overview, and a search that returns no results is not charged.

What are the rate limits for the GoCodebook API?

The GoCodebook free sample is rate-limited per address and paid searches draw from a prepaid balance. See the developer documentation at https://gocodebook.com/developers for current limits and pricing.

Is there a GoCodebook MCP server?

You do not need an MCP server to give your agent the GoCodebook API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.

Can I limit what my agent is allowed to do with the GoCodebook API?

Yes. Write a rule that allows only the search and jurisdiction-list operations, so the agent can search ordinances and check coverage, and every call it makes is logged. Every GoCodebook operation is a read, so nothing it calls changes data.

How do I search ordinances with the GoCodebook API through Jentic?

Search Jentic for 'search California local ordinances', and it returns the GoCodebook search operation with its input schema. Your agent sends the query and jurisdiction and reads back the cited excerpts. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GoCodebook API

AI ReadinessNon-Ready (F)37/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer5 EndpointsREST

For Agents

Search California city and county ordinances and get structured results with verbatim excerpts, citations, and links, plus jurisdiction coverage lookups.

Use for: Search for a city's noise ordinance, Find the local code on short-term rentals in a county, List the California jurisdictions covered, Get one jurisdiction and its local codes

Not supported: Does not provide legal advice, draft documents, or cover federal or out-of-state law. Use for searching California city and county ordinances and returning cited excerpts only.

The GoCodebook API searches California local ordinances, the city and county codes, and returns structured results with verbatim excerpts, citations, and links. A search can be run as a POST body or as a GET query string, and a keyless free sample is available at a per-address rate limit while paid searches add an AI overview. It also lists the cities and counties it covers, returns one jurisdiction with the local codes held for it, and exposes topic ids reserved for state law.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

60%

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.

65%

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: FSignals: 4

15%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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: D-Signals: 1

40%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GoCodebook API to your agent

Capabilities

Start building with GoCodebook API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

GoCodebook API

Jentic AI Readiness Score

GoCodebook 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