Connect Deshen to your AI assistant.

1What the connector is.

Deshen exposes the public-record check as a connector your AI assistant can call. Your assistant does the reasoning; Deshen supplies the evidence and keeps what you decide. The connector is bounded: seven specific tools, no open-ended surface, so what your assistant can do is predictable and auditable. Deshen does not reason on your behalf inside the connector, and does not make up a party, an amount, a date or a contact. Inferred values come back labeled inferred; a source it could not reach comes back marked not read.

2How access works.

Access is per firm. You request access, we issue your firm’s key, and the connector is live the same day. Everything your firm saves lands under that key’s tenancy and nowhere else.

3What you will need.

A Claude plan that supports custom connectors (Pro, Max, Team or Enterprise), or Microsoft Copilot with Copilot Studio for connecting an external tool server, which is an IT step. And your Deshen firm key. That is all.

4The seven tools.

Bounded by design. Five read, two keep.

Read:

• resolve_address: a New York City street address to its lot (BBL). One lot on an exact match; candidates for you to choose from when the address is ambiguous; never a guess.
• get_target_evidence: the public-record pack on one lot. Every recorded instrument with its parties and roles, which satisfaction clears which mortgage, HPD, DOB and ECB violations, 311 by agency, marshal evictions, lien-sale listings, owner of record. Every section labeled, with its source and time of read, totals from the source.
• get_my_pipeline: your firm’s saved lots with their latest conclusion, reason, note and status.
• get_whats_changed: what changed on your saved lots since you last looked. Today: the inferred-maturity clock and the lien-sale stage. Recorded instruments and party changes are next.
• get_why_now: the time-pressure view over Deshen’s scored set of Fannie-financed multifamily lots, by inferred maturity and lien stage. Useful for origination desks; a verification check does not need it.

Keep (both return the persisted entry, so your assistant can confirm the write landed):

• record_disposition: saves your conclusion on a lot: pursue, watch, pass, needs review, data issue, with a reason such as record consistent, subsequent encumbrance, satisfaction mismatch, owner mismatch, tax delinquent, violation load or unverified principal.
• advance_status: moves a lot through your book: new, under review, exception, monitoring, closed, and the origination stages for teams that use them.

5How each line is labeled.

Every field comes back with a label. Verified: a city record as filed, with its source and time of read. Inferred: derived, such as a maturity from a recording date plus a term; a hypothesis to confirm, never asserted. Flagged for verification: a name read off a scanned instrument; confirm against the record before use. Not read: a source Deshen could not reach, marked as not read rather than shown as a zero. Your assistant sees the labels and carries them into its reasoning, so a maturity it cannot verify reaches you as a hypothesis, not a fact.

6Setup in Claude.

Customize, then Connectors, then Add custom connector. Name: Deshen. Remote MCP server URL: https://api.deshen.ai/mcp. Authentication: No sign-in (if Claude pre-selects Sign in now, change it). Request headers: name authorization, value Bearer followed by a space and your firm key, marked Required. Add. If your dialog shows no Request headers section, use the URL we send you with the key included, No sign-in, no headers. Open a new chat, turn Deshen on, and ask it to check an address. The key cannot be edited after adding; a new key means removing the connector and adding it again.

Setup in Copilot.

Your IT team adds Deshen in Copilot Studio as an external tool server at the same URL, authenticated with your firm key. We supply the details on request.

7A typical exchange.

Three moves, from the chat. Shown with Claude; the same tools work in any MCP-capable assistant.

8Your data.

The connector authenticates as your firm. Your saved lots, conclusions, statuses and notes are scoped to your firm and never visible to another firm. Public records are read live and not stored. Anything used to improve the product is permissioned and derived, never your documents, borrowers or book.

9Help.

Access, keys and setup are handled with you directly. Not a design partner yet? Request access.