API and MCP server

Plug the tower registry into your own systems and AI tools. The MCP server answers anyone in public mode; full records, the REST API, the change feed and webhooks come with Enterprise.

MCP server (AI tools)

Connect TowerCensus to Claude, ChatGPT or your own agent. The server is https://towercensus.com/api/mcp (Streamable HTTP). Without a key it answers in public mode: summaries with a link to each record, 5 results per call. With an Enterprise key it returns full records, change history and the change feed.

{
  "mcpServers": {
    "towercensus": {
      "type": "http",
      "url": "https://towercensus.com/api/mcp",
      "headers": { "Authorization": "Bearer tck_live_…" }
    }
  }
}

Tools: search_towers, get_towers, recent_changes (Enterprise), about.

REST API (Enterprise)

Create a key under Account → API keys, then send it as Authorization: Bearer tck_live_…. JSON responses; keyset paging with cursor; up to 100 records per page and 120 requests a minute per key.

curl -H "Authorization: Bearer $KEY" \
  "https://towercensus.com/api/v1/towers?state=TX&limit=100"

Endpoint	What it returns
`GET /api/v1`	datasets, filters, your limits
`GET /api/v1/towers`	FCC-registered antenna structures: height, coordinates, owner, structure type, FAA study and lighting codes. Filters: `statecounty_codestatusstructure_type`
`GET /api/v1/towers/{registration_number}`	one antenna structure + its last 20 changes
`GET /api/v1/changes`	change feed: new, updated, removed records (`dataset`, `after_id`, `since`)

Bulk files and webhooks

Enterprise includes every national and state file (gzipped CSV, refreshed weekly), and any alert can post to your webhook, signed with X-Census-Signature: t=…,v1=HMAC-SHA256(secret, t.body).