DESHEN DOCS
Connect Deshen to your AI agent
1. What the connector is
Deshen exposes its origination intelligence as a connector your AI agent can call. Your agent does the reasoning; Deshen supplies the evidence and saves what you decide. The connector is bounded: six specific tools, no open-ended "ask anything" surface, so what your agent can do is predictable and auditable.
Deshen never reasons on your behalf inside the connector, and never fabricates an owner, amount, date, or contact. Inferred signals come back labeled as inferred.
2. How access works
Onboarding is white-glove. We set up the connector with your team, working with your environment, end to end.
3. What you'll need
A Deshen design-partner workspace (we set this up for your firm).
An MCP-capable AI client — Claude, or any tool that supports MCP.
That's it on your side. Firm-scoped access — so your decisions land in your workspace and nowhere else — is issued and configured during onboarding.
4. The six tools
Bounded by design. Four read, two capture.
Read
get_why_now
Returns time-urgent ranked targets, tiered: act now, approaching, on the clock. Maturity- and lien-led.
get_target_evidence
Returns the full evidence for one building (by BBL), with every field labeled verified or inferred, and the verification gaps named.
get_my_pipeline
Returns your firm's worked targets and their current disposition and status.
get_whats_changed
Returns targets that crossed an urgency boundary since you last touched them.
Capture
(both return the persisted entry, so your agent can confirm the write landed)
record_disposition
Records pursue / watch / pass / needs review / data issue, with a reason code.
advance_status
Moves a target through pipeline status: new → reviewed → watchlist → outreach queued → outreach sent → responded → underwriting started → active opportunity → closed.
5. The honesty contract (why get_target_evidence looks the way it does)
Every evidence field comes back with its trust level attached:
Verified
Sourced from an authoritative NYC public record.
Inferred
A hypothesis (for example, a loan matched to a building by fuzzy Fannie Mae BBL match). Treated as missing verification until you confirm it. Never asserted as fact.
Flagged
Owner names are OCR-extracted from the public record and can be garbled, so Deshen marks them unverified. Confirm the contact before outreach rather than trusting a possibly-wrong name.
Your agent sees these labels and carries them into its reasoning, so a maturity it can't verify is presented to you as an inferred capital-need hypothesis, not a fact.
6. How setup works
Onboarding is white-glove. We set up the connector with your team, working with your environment, end to end:
We provision your firm's workspace and issue firm-scoped access.
We connect the tools to your agent — the six Deshen tools appear in your client, ready to call.
You confirm it's live — ask your agent for the why-now queue and watch real ranked targets come back.
No config files to edit, no credentials to manage by hand. The full technical setup is handled with you during onboarding.
7. A typical exchange
The loop is three moves (pull, reason, capture), all from the chat. Shown here with Claude; the same tools work in any MCP-capable agent:
You: Which NYC multifamily targets have maturity pressure right now?
Claude: [calls get_why_now] Three are in the act-now tier. The strongest is Demo Target A (signal 82) — a verified tax-lien signal at 90-day notice, plus a loan maturity around 5 months out. Note the maturity is inferred from a fuzzy Fannie match — treat it as a hypothesis, not a confirmed date.
You: Mark it pursue and queue it for outreach.
Claude: [calls record_disposition, advance_status] Done — recorded pursue and moved it to outreach queued in your workspace. It'll show in your pipeline, and you'll see it flagged if anything changes.
Notice Claude carried the inferred-maturity caveat without being told to. That's the connector working as intended: Deshen labels the trust level, your agent respects it.
8. Your data
The connector authenticates as your firm. Your dispositions, statuses, and notes are scoped to your workspace and never visible to other firms. Anything used to improve the product is permissioned and derived, never your private documents, relationships, or pipeline.
9. Help
Setup and access are handled through your design-partner onboarding.
Not a partner yet?