Your research, connected.

1. Create your key

Sign in and open Account & connections. Choose “Read saved work” or “Read and create site briefs,” then copy your key. It appears once. Store it in your client's secret settings or an environment variable.

Existing Cividian keys with the read scope can read your briefs if created from a verified account. Creating briefs requires the additional diligence.write scope. Revoke unused keys from your account.

2. Connect through MCP

In a client that supports remote HTTP MCP servers and bearer authentication, add this server URL and authorization header:

URL: https://www.cividian.com/mcp
Authorization: Bearer YOUR_CIVIDIAN_KEY

Available site tools: diligence_resolve_site, diligence_create_brief, diligence_list_briefs, and diligence_brief. Cividian's city intelligence tools are available through the same server.

A client that only offers OAuth cannot use this bearer-key connection. Use its custom-header settings if available. Never paste a key into a conversation.

Or use the REST API

Set CIVIDIAN_API_KEY privately in your terminal or secret manager, then list your saved briefs:

curl https://www.cividian.com/api/v1/diligence/saved \
  -H "Authorization: Bearer $CIVIDIAN_API_KEY"

Create a new brief:

curl https://www.cividian.com/api/v1/diligence/briefs \
  -H "Authorization: Bearer $CIVIDIAN_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"query":"115 W Washington St, Muncie, IN","objective":"residential_infill"}'

Read a brief using GET /api/v1/diligence/briefs?id=YOUR_BRIEF_ID. Responses contain an ok field. A business refusal may use HTTP 200 with ok: false; always check both the status and response.