Crexi Integration Hub

SOURCE MISSING — no KB dir. Authored from crmls/propstream adjacency only.

STATUS: SOURCE MISSING. No workspace/knowledge-base/crexi/ directory exists as of 2026-05-04. This hub is a reference-only placeholder. Crexi is a named external commercial real estate marketplace and data source referenced in deal-ingestion workflows, but NO direct API integration exists today. Do NOT build any Crexi integration without first creating the KB directory (G-KB-SYNC-WITH-CLAUDEMD required) and verifying the API.

Before any Crexi API work:

1. Create workspace/knowledge-base/crexi/ directory
2. Add API.md with verified endpoint, auth, and rate limit information
3. Update CLAUDE.md “Platforms with KB docs” line (G-KB-SYNC-WITH-CLAUDEMD)
4. Then update this hub with real data

---

What Crexi is (context only)

Crexi (Commercial Real Estate Exchange, Inc.) is a commercial real estate marketplace and data platform. RERI uses Crexi as a deal source for commercial and multifamily properties alongside InvestorLift, CRMLS, and PropStream. It is referenced in the deal-ingestion workflow as an inbound data source where deal candidates may be identified manually and then imported into HubSpot.

Known usage pattern (inferred from adjacency, not verified API docs):

• Henry or agents browse Crexi → identify deal candidates
• Deal data is manually parsed or copy-pasted → imported via hubspot-deal-ingest createDealFromParsed()
• No automated API scrape of Crexi exists today
• No Crexi webhook or data feed is wired

This is different from InvestorLift (which has a full sync pipeline — see investorlift) and CRMLS (which has MLS data feed access — see crmls). Crexi is effectively a manual data source today.

Quick reference

Field	Value
Vendor	Crexi (Commercial Real Estate Exchange, Inc.)
URL	https://www.crexi.com
KB doc	SOURCE MISSING — no knowledge-base/crexi/ directory
Auth method	NEEDS VERIFICATION — Crexi API terms/availability unknown
Auth credential	n/a (no integration today)
Webhook port	n/a
Webhook handler	n/a
Outbound API base	NEEDS VERIFICATION
Rate limits	NEEDS VERIFICATION
Cost	NEEDS VERIFICATION (Crexi has paid data/API tiers)
Status	planned (reference-only today)

Components

• workspace/knowledge-base/crexi/ — DOES NOT EXIST — create before any integration work
• hubspot-deal-ingest — current path for Crexi deals (manual parse → createDealFromParsed())
• _summary — acquisition agent that may receive Crexi deal candidates
• deal-ingestion — the workflow Crexi feeds into (manually today)

How it is (not) used today

• Current: Manual — Henry identifies Crexi deals visually → copy-paste property details → hubspot-deal-ingest skill → HubSpot acq + dispo pipelines
• No API integration: No script, no webhook, no cron touches Crexi API today
• Planned (if prioritized): Automated Crexi listing search → filter by criteria (price, market, property type) → auto-ingest candidates to HubSpot acq pipeline
• Agents involved: None today (manual path); acquisitions agent is the target consumer if automated
• Failure mode: n/a (no integration)
• Success criteria for future integration: Crexi KB dir exists + API verified + deal candidates auto-ingested with correct field mapping

Cross-links

Agents that touch this

• _summary — target consumer for any Crexi deal candidates
• _summary — may receive Crexi deal mentions in inbound messages

Skills that invoke this

• hubspot-deal-ingest — current manual path for Crexi deal import via createDealFromParsed()
• il-marketplace-pull — analogous automated pipeline for InvestorLift (reference pattern for future Crexi automation)

Plans that govern this

• vendor-deep-audit-comprehensive-2026-05-02 — Crexi not in vendor baseline (no KB)
• openclaw-self-improvement-layer-2026-05-03 — deal source diversification is OSIL scope

Feedback rules

• feedback_kb_sync_with_claude_md — G-KB-SYNC-WITH-CLAUDEMD: must create KB dir before integration
• feedback_no_plaintext_creds — any future Crexi API key must go in 1Password
• feedback_audit_before_architect — verify Crexi API existence and terms before planning integration

KB / source docs

• SOURCE MISSING — no knowledge-base/crexi/ directory; create before any work
• Adjacent KB (for pattern reference only): README, README, README

System maps

• deal-lifecycle-map — Crexi feeds deal-ingestion (manually today)
• external-integrations — Crexi listed as external data source node (no API line today)

Related: Real estate data platform cluster

Crexi sits in the same market data cluster as CRMLS, PropStream, and InvestorLift — all are deal-source platforms feeding the acquisitions pipeline. For the current automated data layer, see:

• investorlift — full sync pipeline (IL API + Mac Ultra scraping)
• crmls — MLS data feed (CRMLS + RESO API)
• propstream — PropStream API for deal enrichment

Crexi is the only one of the four with no current API integration. Prioritize AFTER InvestorLift AI replication (osil-il-ai-replication-2026-05-03) and CRMLS integrations are stable.

Related: Credential layer cluster

No credentials exist today. When integration is built: store API key as op://Aurora/crexi/api-key. See 1password for op:// CLI access pattern. Follow G-NO-PLAINTEXT-CREDS from day one.

Open issues / TODOs

• BLOCKER: Create workspace/knowledge-base/crexi/ with API.md before any integration work — G-KB-SYNC-WITH-CLAUDEMD requires same-change CLAUDE.md update
• Verify whether Crexi has a public API or only partner/enterprise data access (check https://www.crexi.com/developers or contact Crexi sales)
• Assess Crexi API cost tier vs value of automated ingestion vs manual copy-paste path
• If Crexi API is viable: design automated ingestion pipeline modeled on il-marketplace-pull with IL as the reference implementation
• Confirm Crexi deal types in use at RERI (commercial? multifamily? land?) to scope field mapping in createDealFromParsed()

Recent activity

• 2026-05-04: hub created (W3-S5, Wave 3) — SOURCE MISSING flagged; reference-only placeholder; no integration today