canibuild API
67
AI ReadinessAI-Aware (B)67/100
Agent-ready OpenAPI document · curated by JenticData EnrichmentAddress ValidationapiKey3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up building permits and zoning rules for a property address, and submit permit requests for new construction projects. Useful for site feasibility checks and pre-construction due diligence.
Use for: Check whether a property address has any open building permits, I want to look up the zoning classification for a residential address, Submit a building permit request for a new garage at a given address, Find all permits issued for a specific street
Not supported: Does not handle architectural design, contractor sourcing, or payment for permit fees - use for permit search and zoning lookups only.
Jentic publishes the only available OpenAPI specification for canibuild API, keeping it validated and agent-ready. The canibuild API provides building permit and zoning information for property addresses, allowing applications to check what can be built on a parcel before drafting plans. It exposes endpoints for searching existing permits, lodging permit requests, and looking up zoning rules tied to an address. Builders, real estate platforms, and design tools use it to surface feasibility data without manually scraping municipal records.
Install Jentic One Beta
Connect the canibuild API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the canibuild 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.
1
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%2Fcanibuild.com%2Fcanibuild" | sh2
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%2Fcanibuild.com%2Fcanibuild" | 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.
Capabilities
What an agent can do with canibuild API.
Search existing building permits filed for a given address or project type
Submit a new building permit request with project metadata
Retrieve zoning classification and restrictions for a specific address
Surface pre-construction feasibility data inside design and quoting tools
Validate whether a proposed structure fits zoning rules before drafting plans
Use Cases
Patterns agents use canibuild API for, with concrete tasks.
★ Pre-Construction Feasibility Check
Before a builder quotes a job, they need to know whether the proposed structure is allowed on the parcel. The canibuild API returns zoning classification and existing permit history for a supplied address, so a quoting tool can flag projects that will hit zoning blockers early. This shortens the back-and-forth with councils and avoids quoting work that cannot proceed.
Call GET /zoning with address=123 Main St and return the zoning classification along with any existing permits from GET /permits for that address.
Permit Submission Workflow
Construction admin tools can lodge permit requests directly through POST /permits with the project address and project type. This removes the manual portal entry step from a workflow and gives the team an audit trail of submission attempts and their statuses. Integration is suitable for builder back-office tools that already capture project data.
POST /permits with address and projectType=garage to lodge a new permit request and return the response payload.
Real Estate Listing Enrichment
Real estate platforms can call the zoning endpoint to display what a buyer is allowed to build on a listed property. Listings show zoning classification and any active permit history, helping buyers evaluate development potential before making an offer. This data appears alongside the standard listing fields on the property page.
For each listing address, call GET /zoning and GET /permits and attach the returned zoning class and permit count to the listing record.
AI Agent Construction Assistant
An agent advising on home improvement projects calls canibuild via Jentic to verify zoning and permit status before recommending a contractor or quoting timeline. The agent uses Jentic to discover the right operation by intent, loads the schema, and executes the call without managing canibuild credentials directly.
Search Jentic for 'check building permits at an address', load the searchPermits operation schema, and execute it for a user-supplied address.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for canibuild api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/permits
Search building permits
POST
/permits
Request a building permit
GET
/zoning
Get zoning information for an address
GET
/permits
Search building permits
POST
/permits
Request a building permit
GET
/zoning
Get zoning information for an address
Jentic AI Readiness Score
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.
C
canibuild API
- AI-Aware (B)67/100
87
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 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).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the canibuild API by hand means setting its Authorization key header and calling the permit and zoning routes yourself. Through Jentic you install once, import canibuild from the API Directory, store the key once, and your agent calls it.
Permission scoping
canibuild takes its permit and zoning inputs as parameters rather than as a resource in the URL path, so limit the agent to the operations it needs, such as permit and zoning searches. You choose the operations it may call, so creating a permit is not included unless you add it.
Credential isolation
Your canibuild API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check zoning for an address' or 'search building permits', and Jentic returns the matching canibuild operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using canibuild API through Jentic.
Why is there no official OpenAPI spec for canibuild API?
canibuild does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call canibuild API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the canibuild API use?
The canibuild API uses an API key passed in the Authorization header. Through Jentic, the key is stored in the encrypted vault and the agent receives a scoped token, so the raw key never enters the agent's prompt context.
Can I look up zoning rules for a specific address with the canibuild API?
Yes. Call GET /zoning with the address as a query parameter and the response returns the zoning classification tied to that address.
How do I submit a building permit request through Jentic?
Search Jentic for 'request a building permit', load the requestPermit operation, then execute POST /permits with address and projectType in the request body.
What are the rate limits for the canibuild API?
The OpenAPI spec does not publish explicit rate limits. Treat as a low-volume third-party endpoint and implement client-side backoff on 429 responses; check canibuild's portal for current quotas.
Does the canibuild API cover regions outside the listed addresses?
Coverage depends on which municipal records canibuild has indexed. The /permits and /zoning endpoints accept any address string but return data only where canibuild has source records, so verify coverage for your target region before depending on it.
Can I limit what my agent is allowed to do with the canibuild API?
Yes. Because you run Jentic One yourself, you decide which canibuild operations your agent may call and which credentials it uses, so you can allow the read-only lookups like GET /permits and GET /zoning while leaving out the POST /permits operation that lodges a new permit request. The canibuild API takes its address and project inputs as parameters rather than as resources in the URL path, so you scope by choosing the operations the agent may invoke rather than by path. Your stored API key is injected at execution time under your own rules, and the agent only ever reaches the endpoints you have permitted.
GET STARTED