CREXi

CREXi (Commercial Real Estate Exchange, Inc.) is a Los Angeles-based commercial real estate marketplace and data platform founded in 2015, operating a sales marketplace, lease marketplace, auction platform, Broker PRO tools and the Crexi Intelligence property-records product. Its API surface is partner-gated rather than self-serve: the Crexi Listing API is a one-way syndication feed that lets MLSs, Realtor Boards, brokerages and data providers push listings into the marketplace (RESO, RETS, WebAPI and XML feeds, synced daily, with Crexi stating 100% compliance with the RESO Data Dictionary and 100+ partner organizations), while the Crexi Exchange API is documented in a password-protected Theneo portal at api-docs.crexi.com and fronted by an API-key-gated Swagger UI at exchange.crexi.com. The platform API host api.crexi.com publishes anonymous OpenID Connect and OAuth 2.0 authorization-server discovery documents.

CREXi is listed with 3 APIs on the APIs.io network. Tagged areas include Real Estate, Commercial Real Estate, Marketplace, Property Data, and Listings.

CREXi’s developer surface includes API reference, documentation, getting-started guide, support, engineering blog, pricing, signup flow, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.2/100 thin ▬ flat Agent 7/100 agent aware Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

3 APIs 1 MCP Servers

Real Estate Commercial Real Estate Marketplace Property Data Listings Auctions Market Intelligence Data Syndication RESO Company

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 35.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 8.7 / 17

Operational Transparency 2.1 / 11

Contract Governance 1.9 / 10

Discoverability 5.9 / 9

Regulatory Posture 4.3 / 15

Agent readiness — 7/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/crexi/"><img src="https://apis.io/badge/crexi/card.svg" alt="CREXi on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Operational Transparency scores 19.0 — up to +10.5 composite points Ask about this →
Contract Governance scores 18.2 — up to +9.8 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/crexi/apis.yml: open an issue on github.com/api-evangelist/crexi to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Crexi Exchange API

The Crexi Exchange API is Crexi's partner-facing REST API, documented in a Theneo-published portal at api-docs.crexi.com (password protected) and fronted by a Swagger UI gateway...

Crexi Platform API

The api.crexi.com host is the platform API backing the Crexi web and mobile applications. It anonymously publishes OpenID Connect discovery (/.well-known/openid-configuration) a...

Crexi Listing API

The Crexi Listing API is a one-way data sync that lets qualifying organizations — MLSs and Realtor Boards, large brokerages and franchise networks, and real estate data provider...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

CREXi MCP Server

MCP SERVER

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

CREXi

11 quoted statements, read from CREXi's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

CREXi

20 quoted statements, read from CREXi's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

CREXi

3 quoted statements, read from CREXi's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

CREXi

1 quoted statement, read from CREXi's own page on 2026-11-09.

AI PREFS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

CREXi

2 quoted statements, read from CREXi's own page on 2026-11-09.

LICENSE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

CREXi Authentication

apiKey/http/oauth2/openIdConnect · 5 schemes

SECURITY

CREXi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

CREXi Scopes

2 scopes · password/refresh_token/switch_user/single_use_token_exchange

2 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 3

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

AIPreferences

AIPreferences

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Conventions

Conventions

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 5

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

DataLicense

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 4

Properties that don't map to a standard resource type

Research

Podcast

DataProcessing

Eligibility

Source (apis.yml)

aid: crexi
name: CREXi
description: 'CREXi (Commercial Real Estate Exchange, Inc.) is a Los Angeles-based commercial real estate marketplace and
  data platform founded in 2015, operating a sales marketplace, lease marketplace, auction platform, Broker PRO tools and
  the Crexi Intelligence property-records product. Its API surface is partner-gated rather than self-serve: the Crexi Listing
  API is a one-way syndication feed that lets MLSs, Realtor Boards, brokerages and data providers push listings into the marketplace
  (RESO, RETS, WebAPI and XML feeds, synced daily, with Crexi stating 100% compliance with the RESO Data Dictionary and 100+
  partner organizations), while the Crexi Exchange API is documented in a password-protected Theneo portal at api-docs.crexi.com
  and fronted by an API-key-gated Swagger UI at exchange.crexi.com. The platform API host api.crexi.com publishes anonymous
  OpenID Connect and OAuth 2.0 authorization-server discovery documents.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
image: https://learn.crexi.com/hubfs/crexi%20logo%20navy%20text.svg
url: https://raw.githubusercontent.com/api-evangelist/crexi/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- Real Estate
- Commercial Real Estate
- Marketplace
- Property Data
- Listings
- Auctions
- Market Intelligence
- Data Syndication
- RESO
- Company
tags_raw:
- Real Estate
- Commercial Real Estate
- Marketplace
- Property Data
- Listings
- Auctions
- Market Intelligence
- Data Syndication
- RESO
- Company
- Real-Estate
apis:
- aid: crexi:crexi-exchange-api
  name: Crexi Exchange API
  description: The Crexi Exchange API is Crexi's partner-facing REST API, documented in a Theneo-published portal at api-docs.crexi.com
    (password protected) and fronted by a Swagger UI gateway at exchange.crexi.com. The OpenAPI document is served at /swagger/docs/v1
    behind an API-key login gate; the published login script declares the scheme as an apiKey named x-api-key passed in the
    request header.
  humanURL: https://api-docs.crexi.com/
  baseURL: https://exchange.crexi.com
  tags:
  - Commercial Real Estate
  - Listings
  - Partner API
  properties:
  - type: APIReference
    url: https://api-docs.crexi.com/
  - type: Authentication
    url: authentication/crexi-authentication.yml
  - type: Conventions
    url: conventions/crexi-conventions.yml
  x-contract-discovery:
    openapi_url: https://exchange.crexi.com/swagger/docs/v1
    http_status: 302
    gated: true
    gate: API-key login (redirects to /static/auth.html)
    note: Real OpenAPI/Swagger surface confirmed present but not publicly retrievable; nothing was saved to openapi/ because
      no spec body could be fetched.
- aid: crexi:crexi-platform-api
  name: Crexi Platform API
  description: The api.crexi.com host is the platform API backing the Crexi web and mobile applications. It anonymously publishes
    OpenID Connect discovery (/.well-known/openid-configuration) and OAuth 2.0 authorization server metadata (RFC 8414), exposes
    a JWKS document and a /token endpoint, and returns an ASP.NET Core health-check payload at /health. A Swashbuckle Swagger
    UI is present at /swagger but is protected by HTTP Basic authentication.
  humanURL: https://api-docs.crexi.com/
  baseURL: https://api.crexi.com
  tags:
  - Platform API
  - OpenID Connect
  - OAuth
  - Authentication
  tags_raw:
  - Platform API
  - OpenID Connect
  - OAuth 2.0
  - Authentication
  properties:
  - type: Authentication
    url: authentication/crexi-authentication.yml
  - type: OAuthScopes
    url: scopes/crexi-scopes.yml
  - type: WellKnown
    url: well-known/crexi-well-known.yml
  - type: OpenIDConnect
    url: well-known/crexi-openid-configuration.json
  x-contract-discovery:
    openapi_url: https://api.crexi.com/swagger/v1/swagger.json
    http_status: 401
    gated: true
    gate: 'WWW-Authenticate: Basic'
- aid: crexi:crexi-listing-api
  name: Crexi Listing API
  description: The Crexi Listing API is a one-way data sync that lets qualifying organizations — MLSs and Realtor Boards,
    large brokerages and franchise networks, and real estate data providers — automatically push their listings onto Crexi.com.
    Crexi accepts RESO, RETS, WebAPI and XML feeds, listings sync daily, and Crexi states it is 100% compliant with the RESO
    Data Dictionary across 100+ partner organizations. Access is granted through integrations@crexi.com after a data and legal
    review, execution of a Listing API agreement, API token issuance and staging-environment testing.
  humanURL: https://learn.crexi.com/listing-api-overview-crexi-help-center
  tags:
  - Data Syndication
  - RESO
  - Listings
  properties:
  - type: Documentation
    url: https://learn.crexi.com/listing-api-overview-crexi-help-center
  - type: Conformance
    url: conformance/crexi-conformance.yml
  x-access:
    model: partner-onboarded
    contact: integrations@crexi.com
    note: No public base URL is published; the endpoint and API token are provisioned per partner during onboarding, so no
      baseURL is asserted here.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: MCPServer
  url: mcp/crexi-mcp.yml
- type: DomainSecurity
  url: security/crexi-domain-security.yml
- type: Website
  url: https://www.crexi.com/
- type: DeveloperPortal
  url: https://api-docs.crexi.com/
- type: APIReference
  url: https://api-docs.crexi.com/
- type: Documentation
  url: https://learn.crexi.com/listing-api-overview-crexi-help-center
- type: GettingStarted
  url: https://learn.crexi.com/crexi-basics
- type: Support
  url: https://learn.crexi.com/
- type: Blog
  url: https://www.crexi.com/blog/
- type: GitHubOrganization
  url: https://github.com/crexi-dev
- type: Pricing
  url: https://www.crexi.com/broker-plans
- type: SignUp
  url: https://www.crexi.com/signup
- type: Login
  url: https://admin.crexi.com/account/login
- type: TermsOfService
  url: https://www.crexi.com/msa/
- type: PrivacyPolicy
  url: https://www.crexi.com/privacy
- type: StatusPage
  url: https://status.crexi.com/
- type: Lifecycle
  url: lifecycle/crexi-lifecycle.yml
- type: Authentication
  url: authentication/crexi-authentication.yml
- type: OAuthScopes
  url: scopes/crexi-scopes.yml
- type: WellKnown
  url: well-known/crexi-well-known.yml
- type: Conformance
  url: conformance/crexi-conformance.yml
- type: Conventions
  url: conventions/crexi-conventions.yml
- type: Packages
  url: packages/crexi-packages.yml
- type: LLMsTxt
  url: llms/crexi-llms.txt
- type: Research
  url: https://research.crexi.com/
- type: Podcast
  url: https://podcast.crexi.com/
- type: UsageTerms
  url: terms/crexi-terms-of-service.yml
- type: DataProcessing
  url: privacy/crexi-privacy-policy.yml
- type: Eligibility
  url: eligibility/crexi-eligibility.yml
- type: AIPreferences
  url: ai-preferences/crexi-ai-preferences.yml
- type: DataLicense
  url: data-license/crexi-data-license.yml
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 13
  pass: local-v1

CREXi API — frequently asked questions

Does CREXi have an API?

Yes. APIs.io lists 3 APIs from CREXi, including Crexi Exchange API, Crexi Platform API and Crexi Listing API.

How do I authenticate with the CREXi API?

CREXi documents its authentication (apiKey/http/oauth2/openIdConnect · 5 schemes). The details are profiled on APIs.io as CREXi Authentication.

Does CREXi have an MCP server?

Yes. APIs.io lists 1 MCP server for CREXi.

Is the CREXi API ready for AI agents?

CREXi has a Kin Score of 35.2 out of 100 (thin) and an Agent Readiness score of 6.5 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/crexi"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/crexi/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/crexi/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.