API

Build on Entitlement Intelligence

Structured, source-anchored development-code data for feasibility and entitlement workflows — in developer preview now.

Apply for API preview →View API Documentation

Entitlement Agent · MCP

In Development

Connect Your AI Agents to Municipal Code Intelligence

LocalCode MCP gives authorized AI agents direct, source-backed access to municipal code intelligence — grounded in normalized data, not general web search or model knowledge.

API

Structured programmatic access for applications and data systems.

MCP

Agent-native access for LLMs and internal entitlement workflows.

Discuss an MCP Pilot →View API Access Options

Entitlement Agent · LocalCode MCP

Entitlement Agent

Question:

Does Austin § 25-2-779 impose an interior side-yard requirement for this project?

Project facts:

• Jurisdiction: Austin
• Base zoning:  SF-4A
• Adjacent:     SF-4A

LocalCode MCP Response

{
  "result": "conditional_exception",
  "standard": {
    "dimension": "interior_side_yard",
    "requirement_ft": 5
  },
  "exception": {
    "applies_when": "adjacent property is zoned SF-4A",
    "effect": "side-yard requirement waived"
  },
  "source": {
    "citation": "Austin Code § 25-2-779(D)",
    "verification_status": "verified"
  }
}

The API Surface

Structured Responses, Not Summaries

Every endpoint returns source-anchored regulatory data — code text, hierarchy, effective dates, and the ordinance behind each value — so your application never has to parse prose to find an answer.

Source Verification · tx-austinjson

{
  "section_id": "25-2-773",
  "section_title": "Permitted Uses — MF-3",
  "jurisdiction": "tx-austin",
  "feasibility_signals": {
    "regulatory_domain": "zoning_land_use",
    "rule_type": "use_permission",
    "entitlement_relevance": true
  },
  "source_verification": {
    "effective_date": "2022-03-14",
    "source_ordinance": "20220127-069",
    "source_url": "https://data.localcode.ai/sources/tx-austin/20220127-069.pdf"
  },
  "amendments": [
    {
      "ordinance": "20231109-152",
      "date": "2023-11-09",
      "description": "Updated permitted use language"
    }
  ]
}

GET/v1/jurisdictionsJurisdictions

GET/v1/code-sections/{id}Code Sections

GET/v1/ordinances/{id}Ordinances

GET/v1/legislative-chainLegislative Chain

GET/v1/source-verificationSource Verification

GET/v1/sourcesSources

GET/v1/searchSearch

Technical Foundations

Built for Production Integration

Authentication	Bearer token in the Authorization header, scoped per environment. Access is by application only — no self-serve keys today.
OpenAPI Spec	A published spec you'll be able to import into Postman, Insomnia, or any OpenAPI client.
Performance	Low-latency, per-jurisdiction cached reads with batch-friendly endpoints for bulk lookups.
SDKs	TypeScript and Python clients for analytics pipelines and PropTech platforms.
Webhooks	Structured change-event delivery with automatic retry, delivery logs, and event replay.

Interested in early API access?

API access is manually approved — tell us what you're building and we'll evaluate your application directly.

Developer Preview: Features and payloads are iterative.

Apply for API preview →View API Documentation