Developer API

1. Sign up and upgrade to Analyst Solo, Analyst Team, or Platform Developer.
2. Create an API key in your dashboard.
3. Call any endpoint with Authorization: Bearer imc_….

curl "https://nmycity-api.onrender.com/api/v1/data/products/neighborhood-safety?\
scope=city&scopeId=2507000&start=2024-01-01&end=2024-12-31" \
  -H "Authorization: Bearer imc_YOUR_API_KEY"

Connect nMyCity from Cursor, Claude Desktop, or any MCP host. We ship two stdio servers — both thin clients over the same REST API, with the same auth, quotas, and attribution.

Beta: MCP packages are not on npm yet. Build from the monorepo (npm run build:mcp:all) and point your MCP host at node packages/mcp-server/dist/index.js and node packages/beacon-mcp/dist/index.js. npm publish is planned for general availability.

Local Cursor config (monorepo)

{
  "mcpServers": {
    "inmycity": {
      "command": "node",
      "args": ["packages/mcp-server/dist/index.js"],
      "env": {
        "INMYCITY_API_URL": "https://nmycity-api.onrender.com",
        "INMYCITY_API_TOKEN": "imc_YOUR_API_KEY"
      }
    },
    "inmycity-beacon": {
      "command": "node",
      "args": ["packages/beacon-mcp/dist/index.js"],
      "env": {
        "INMYCITY_API_URL": "https://nmycity-api.onrender.com",
        "INMYCITY_API_TOKEN": "imc_YOUR_BUSINESS_API_KEY",
        "INMYCITY_BEACON_ATTESTATION": "prohibited-use-accepted-v1"
      }
    }
  }
}

Env aliases NMYCITY_* also work during the rebrand. Create keys in Dashboard → API keys. Copy .cursor/mcp.json.example to .cursor/mcp.json and run npm run build:mcp:all from the repo root.

Requires Pro, Analyst, or Platform Developer tier. Tools:

• search_places — resolve place_id from address or neighborhood
• query_civic_data — per-domain counts for a scope and date range
• get_neighborhood_safety_bundle — multi-domain safety product in one call
• list_domains — domain catalog

Resources: API docs index, model cards, source freshness.

Separate server for the Civic Beacon API. Requires Business tier, a passing fairness audit on the API deployment, and explicit acceptable-use attestation before the server will start.

Read and accept the Beacon acceptable-use policy before setting NMYCITY_BEACON_ATTESTATION=prohibited-use-accepted-v1 in your MCP config (legacy alias: INMYCITY_BEACON_ATTESTATION; REST clients use header X-nMyCity-Attestation, legacy X-InMyCity-Attestation).

Tools:

• search_places — resolve place_id
• list_beacon_products — product catalog and attestation requirements
• get_place_index — decomposed Neighborhood Trajectory Index + lineage
• get_place_trajectory — current index + historical values
• get_index_validity — O2 out-of-sample backtest report

REST equivalents: GET /api/v1/beacon/index, /trajectory, /validity. Beacon rate limit: 60 requests/min (Business), 120/min (Enterprise).

• API index (JSON)
• OpenAPI 3.0 spec
• Trust & Data — sources and freshness

Responses include X-RateLimit-Limit-Monthly and X-RateLimit-Remaining-Monthly headers. Every payload includes per-domain attribution (source, method, warehouse table).