Skip to help content
AICD API
Article

Introducing AICD API: local government data for builders and AI agents

A launch-day introduction to AICD API: the products builders can create, DFW launch scope, API and MCP integration paths, source-linked records, and a public request to get started.

Give your agent a goal. Start with AICDAPI.com.

We're launching AICD API, an agent-first civic-data platform that turns public local-government records into structured, source-linked data, starting in Dallas-Fort Worth.

If you're building a development tracker, contractor research tool, or local-business briefing, start with what you want to learn. Give your agent the goal and the URL. It can discover supported data, try a public query, decide whether the results fit your project, and recommend a paid plan and integration when they do.

The entire site, including the API, is designed for that workflow. Machine-readable guides explain what's available, browser tools help agents use the site, and REST and MCP interfaces connect the data to your application. You approve the purchase and access setup; your agent can then help build the integration.

See what a public query can find

In an October 3, 2026 check, an agent started at the homepage, found the documentation, queried upcoming zoning items without an account, and followed a result to its detail response and government meeting source.

One returned record described a proposed bar and live-music specific-use-permit amendment at 2640 Elm Street, listed for an October 14 Dallas City Council meeting. It included a summary, evidence quote, location, procedural context, and a government source link.

For a business-monitoring product, that gives the agent a specific place, proposal, and meeting to investigate. The proposal and its current status still need review against the original record, which stays within reach of the reader.

You can inspect public records now. This request returns up to three recent classified agenda hits, with no API key:

curl --fail-with-body --silent --show-error \
  'https://aicdapi.com/api/v1/public/agenda-hits?limit=3'

The response includes fields such as title, jurisdictionName, meetingAt, summary, evidenceQuote, and sourceUrl. The upcoming-hits route supports topic queries and pagination for forward-looking research.

Give your agent the job

Try this with an agent that can read websites and make HTTP requests:

Use https://aicdapi.com to help me build a source-linked briefing on upcoming DFW government decisions that could affect commercial properties or local businesses. Discover the supported data, check freshness and limits, and produce one useful example through the public routes. Explain the gaps. If paid access fits, recommend a plan and integration approach. Ask for my approval before account setup, purchase, or credential creation and configuration.

Change the audience and question to match your project. The first result should help you decide whether the data is worth building around.

Built for agents from the first visit

An agent needs to understand a service before it can recommend or integrate it. AICD API gives it a path through each step:

  • Discover and evaluate. The agent index leads to Markdown guides and an OpenAPI contract covering resources, access requirements, examples, and limits. Six public REST routes support no-key evaluation of coverage research, recent and upcoming agenda hits, individual hits, featured source status, and meeting cadence.
  • Use the website. WebMCP tools use the browser's native document.modelContext API. In a supporting browser, an agent can read documentation, find public resources, and navigate the open site. Signed-in tools can inspect account access and open checkout or billing; a person completes payment.
  • Connect to your application. The customer REST API provides frozen exports, a durable change feed, current-record batch reads, and source-health information. The separate remote MCP server supports standard Streamable HTTP, with tools to check coverage and source health, search agenda records, and read a selected item. Authenticated REST and MCP use scoped API keys.

For a backend integration, your application can start with a snapshot and apply committed changes as they arrive. For an agent-led research workflow, MCP provides tools it can call while working on a question. The browser's WebMCP tools handle the site experience; the remote MCP server handles authenticated civic-data access.

Build around your customer's question

The same source-linked records can support different products:

  • Development trackers: connect related records to a project timeline so people can follow a proposal over time.
  • Contractor research: identify public projects worth investigating and show the stage established by the source.
  • Business monitoring: organize relevant decisions around a company's locations and create review tasks for the people responsible.
  • Research assistants: assemble background briefs for reporters, analysts, or business teams, with evidence readers can open.

You build the workflow and customer experience. AICD API supplies the supported records and source information.

Our launch starts in DFW, with a broader civic-data direction that includes permits, licenses, and inspections. The research coverage catalog maps a dated research pass across 238 active municipalities and 16 counties, including permit and property-tax sources. These are researched sources, not a count of live integrations; the catalog marks ingestion as unverified.

Use the API reference to identify currently supported resources and source status for current health and ingestion evidence on featured meeting sources. Your agent should check the records, accuracy, and freshness your project needs. Missing or stale results should remain a gap to investigate.

Evaluate first, then choose your plan

The no-key public routes let you test fit before account setup. When the results support your idea, have your agent recommend the integration method and plan based on the sources, request volume, and data volume you need.

Monthly plans are Builder at USD 49, Pro at USD 149, and Ultra at USD 499. Builder includes 10,000 admitted requests and 1 GB of response data per month. Feed subscriptions require Pro or Ultra. The usage limits give your agent the details to compare.

The first paid month is charged at signup and the subscription renews monthly. There is no free plan or free trial. Review the recommendation and checkout terms, then authorize the purchase and access setup when you're ready.

Start with one question you want your product to answer. Give your agent the prompt above and AICDAPI.com, and ask it to bring back a result you can inspect.