Skip to help content
AICD API
Prelaunch connection guide

Agent and MCP setup

Prepare a safe Streamable HTTP connection and understand the current beta gate.

Reviewed Sep 15, 2026Owner: AICD APISource: a6e8820Read as Markdown

Current support status

The authenticated server route is built at https://aicdapi.com/api/v1/mcp. It requires a bearer key with mcp:read.

Paid MCP tool calls are not available yet. They return beta_unavailable and tell clients not to retry automatically. No desktop or command-line client is labeled as fully supported until its ordinary-user release test passes.

Connection values for invited testing

  • Transport: Streamable HTTP over HTTPS.
  • Server URL: https://aicdapi.com/api/v1/mcp.
  • Authentication: Authorization bearer header from AICD_API_KEY.
  • Current protocol version: 2026-07-28.
  • The server keeps a stateless compatibility path for the 2025-06-18 initialize flow.
  • Maximum request body: 65,536 bytes. Tool timeout: 10 seconds.
Generic client valuesjson
{
  "url": "https://aicdapi.com/api/v1/mcp",
  "bearerTokenEnvVar": "AICD_API_KEY"
}

Safe setup

  1. Create one mcp:read key for this agent.
  2. Put the secret in the client's secret field or AICD_API_KEY environment variable.
  3. Add the HTTPS server URL and reconnect the client.
  4. When paid beta opens, list tools before making a call and check each returned source link.
  5. Revoke the key when you remove the client.

Search one classified topic

The search_agenda tool requires query. Add topicSlug to select an exact topic slug. A topic slug uses 1 to 64 lowercase letters, numbers, underscores, or hyphens.

Each result includes publisher names and the source type. It also includes the source freshness status and the last successful check time when one exists.

  • The query, topic, jurisdiction, and date filters are combined with AND.
  • A result must have a classified topic match for the exact topicSlug. A word in an agenda title or body does not create that match by itself.
  • Freshness can be healthy, stale, failing, or inactive. Healthy, stale, and failing use the source's expected check interval, last success, and latest failure. Inactive means the source endpoint is no longer scheduled, while its historical records stay searchable.
  • lastSuccessfulCheckAt is the time of the latest successful source check. It is not proof that the source was complete or that a record was published at that time.
  • An empty result does not prove that no government action occurred. Check coverage, the topic slug, the date range, and the government source.
Search one classified topicjson
{
  "query": "data center",
  "topicSlug": "development_approval",
  "jurisdictionSlug": "dallas",
  "fromDate": "2026-09-01",
  "toDate": "2026-09-10"
}

Client compatibility

  • Generic Streamable HTTP configuration is documented from the server contract.
  • Codex, Claude, ChatGPT, and other named clients are pending ordinary-user release checks.
  • Client-specific menus and configuration shapes can change. Follow the client maker's current documentation.

Links