For Agents
Query parcel-level entitlement data, ADU yield, and redevelopment leads for the Silicon Valley Peninsula and South Bay, with code citations.
Use for: List SB 9 eligible parcels in the Peninsula, Find redevelopment leads in the South Bay, Get the entitlement intelligence for a specific property, Pull the latest market signals for a lot
Not supported: Does not handle nationwide coverage, mortgage lending, or title and escrow. Use for Peninsula and South Bay parcel entitlement data only.
The AddressIntel Peninsula Entitlement API returns parcel-level development data for the Silicon Valley Peninsula and South Bay: SB 9 status, ADU yield, and FAR headroom per lot, each citing the municipal code section it came from and the date it was read. Agents can list SB 9 inventory, redevelopment and ADU leads, and market signals, or pull full intelligence for one property by id. Coverage is regional by design, joined to building permits, listings, and comparable sales.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AddressIntel Peninsula Entitlement 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%2Faddressintel.co%2Faddressintel" | shStep 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%2Faddressintel.co%2Faddressintel" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with AddressIntel Peninsula Entitlement API.
List SB 9 inventory for parcels in the covered region
List redevelopment and ADU leads with their yield figures
Pull market signals joined to permits, listings, and comparable sales
Get full entitlement intelligence for one property by id
Register a webhook to receive new leads and signals
Patterns agents use AddressIntel Peninsula Entitlement API for, with concrete tasks.
★ Agent-Driven Parcel Research
A developer's agent researches what can be built on a given lot. The AddressIntel API returns full entitlement intelligence for one property by id, including SB 9 status, ADU yield, and FAR headroom, each with the municipal code section and read date, so the agent reports grounded development potential rather than guesses.
Fetch the entitlement intelligence for a property id and summarize its SB 9 status, ADU yield, and FAR headroom with code citations
Lead Discovery for Developers
An acquisitions team hunts for redevelopment and ADU opportunities across the Peninsula. The AddressIntel API lists redevelopment leads and ADU leads with their yield figures, so an agent can pull a ranked list of candidate parcels and pass the strongest ones to the team.
List current ADU and redevelopment leads in the region and return the parcels with the highest yield
Entitlement Due Diligence
A buyer verifies a parcel's development claims before closing. The AddressIntel API joins SB 9 status and yield to building permits, listings, and comparable sales, and cites the code section and date for each figure, so an agent can assemble a due-diligence summary with its sources attached.
Pull the market signals and entitlement data for a parcel and compile a due-diligence summary with its code citations
8 endpoints — the addressintel peninsula entitlement api returns parcel-level development data for the silicon valley peninsula and south bay: sb 9 status, adu yield, and far headroom per lot, each citing the municipal code section it came from and the date it was read.
METHOD
PATH
DESCRIPTION
/v1/sb9-inventory
List SB 9 inventory
/v1/redevelopment-leads
List redevelopment leads
/v1/adu-leads
List ADU leads
/v1/market-signals
List market signals
/v1/properties/{id}
Get full property intelligence
/v1/webhooks/register
Register a webhook for leads and signals
/v1/sb9-inventory
List SB 9 inventory
/v1/redevelopment-leads
List redevelopment leads
/v1/adu-leads
List ADU leads
/v1/market-signals
List market signals
/v1/properties/{id}
Get full property intelligence
/v1/webhooks/register
Register a webhook for leads and signals
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring AddressIntel by hand means handling its header API key and knowing which endpoints are open and which require it. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which AddressIntel operations your agent may call, so it can read inventory, leads, and property intelligence while the webhook-registration and subscription operations stay out of the set unless you add them.
Credential isolation
Your AddressIntel 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 'get entitlement data for a property' or 'find redevelopment leads', and Jentic returns the matching AddressIntel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using AddressIntel Peninsula Entitlement API through Jentic.
What authentication does the AddressIntel Peninsula Entitlement API use?
The AddressIntel API authenticates with an API key sent in a request header, per its OpenAPI spec. Creating a free key and subscribing to briefings are open, while the data endpoints require the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I get entitlement data for a specific property?
Yes. The API returns full entitlement intelligence for one property by id, including SB 9 status, ADU yield, and FAR headroom, each citing the municipal code section and the date it was read. An agent can pull that record and the related market signals in one research pass.
What are the rate limits for the AddressIntel Peninsula Entitlement API?
The OpenAPI spec does not define rate limits. Check the AddressIntel documentation at https://addressintel.co for the current limits, including any difference between the free tier and a Pro key.
How do I research a parcel through Jentic?
Import the AddressIntel API from the Jentic directory and give your agent an intent such as 'get entitlement data for a property'. Jentic returns the property-intelligence operation with its input schema, your agent supplies the property id and reads the result, and your stored key is injected at execution time. 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 AddressIntel Peninsula Entitlement API?
Yes. Write a rule that allows only the data-read operations, such as listing inventory and leads and reading a property, so your agent cannot register webhooks or change the subscription, and every call it makes is logged.
Is there an AddressIntel MCP server?
You don't need an MCP server to give your agent the AddressIntel API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, so no extra server's tool definitions sit in the agent's context.
GET STARTED