AI TOOL SELECTION
The CoStar Clause That Breaks Claude and ChatGPT Workflows
Can Claude or ChatGPT read CoStar? It comes up on nearly every sourcing call PSV joins: operators pay real money for CoStar and want their AI workflows to use it. The short answer is that CoStar publishes no self-serve API, its license terms prohibit automated extraction in unusually broad language, and the workable pattern is different from what most people first try. Here is what the license actually says, and the workflow that respects it.
Direct answer
Direct answer to can AI access CoStar data
CoStar offers no public self-serve API for CoStar Suite, and its terms prohibit using “any data mining, gathering or extraction tool, or any robot, spider or other automatic device or manual process, to monitor or copy any portion of the Product.” That language covers browser automation, not just scrapers. The legitimate pattern is to work downstream of the product: exports a licensed seat produces in the ordinary course of use, normalized and analyzed by AI after they leave the portal, plus licensed alternatives like Yardi Matrix for market data. Confirm your own license schedule with your CoStar representative and counsel before building anything.

The direct answer on CoStar and AI access
CoStar does not publish a self-serve API for CoStar Suite, LoopNet listing data, or its comps and analytics products. As of this writing PSV finds no publicly documented developer program, and access beyond the logged-in portal runs through commercial conversations with CoStar. That absence is not an oversight. CoStar’s business is licensed data, and its Terms of Use, the license agreement displayed at costar.com, reserve every path to that data. The operative clause prohibits licensees, without express written permission, from using “any data mining, gathering or extraction tool, or any robot, spider or other automatic device or manual process, to monitor or copy any portion of the Product or the data generated from it,” alongside prohibitions on using the product to build any database or product and on providing any portion of it to a competitor.
Two words in that clause deserve more attention than they get: “manual process.” The workaround that comes up most often in PSV’s rooms, teaching an AI agent to click through the portal the way a person would, log in, run a search, export five hundred records at a time, is automation of exactly the kind the sentence reaches, and the browser-driving part does not launder it. CoStar also enforces. In a 2016 press release the company announced a settlement in which RealMassive paid $1 million and acknowledged, in CoStar’s words, systematic misappropriation of CoStar research. Whatever one thinks of the terms, they are the terms, and an AI workflow built on violating a data license is not an asset. It is a liability with a run rate.
What a licensed seat can still do
The license restricts how data leaves the product, not whether a licensed professional can use the product as built. CoStar’s portal ships export functions for licensed users in the ordinary course of use, subject to the caps and conditions in each firm’s license schedule, and those schedules differ by agreement, which is why the only reliable statement about what your seat may export is the one your CoStar representative and your counsel give you. PSV’s point is narrower and holds across schedules: there is a real difference between a person using the product’s own export features for the firm’s internal analysis, and a bot monitoring or copying the product. The first is how the product is sold. The second is what the clause prohibits.
That difference defines where AI legitimately enters: downstream. Once an export produced by a licensed seat is sitting in the firm’s own folder, on the firm’s own systems, the work AI is actually good at begins. Normalizing five hundred rows of inconsistent property records, deduplicating against the firm’s existing pipeline, cross-referencing a region list from an internal Excel file, flagging which sites match a buy box and which fail it and why. None of that touches CoStar’s systems. The product produced a report for a licensed user; the firm’s AI reads the firm’s copy of it. This is the same boundary PSV recommends for Yardi when the connector is unavailable, and it has the same virtue: the AI reads what the system of record already produced under existing controls, and writes nothing back.
The workflow PSV would run
Start with the decision the data feeds, which on most calls is site selection or comp support. The inputs are the export files a licensed analyst produces in the normal course of work, plus the firm’s own deal list and criteria. The workflow normalizes each export into one schema, deduplicates against everything previously exported so the running dataset stays clean, applies the firm’s screening criteria with the arithmetic done in code rather than by the language model, and returns a shortlist memo: which properties cleared, which failed, on which criterion, with every row traced to the export file and date it came from. The reviewer is the analyst who owns the territory. The approval gate is that no owner gets contacted and no LOI moves on a property that a person has not looked at in the portal, because the export is a snapshot and the listing may have moved.
The comparison worth internalizing is between the four paths people actually consider. PSV’s position is the third column, with the fourth as the complement for market data.
| Path | What it is | License posture | PSV read |
|---|---|---|---|
| Browser automation | An agent drives the logged-in portal: searches, pages, exports on a schedule | Prohibited: the terms reach any “automatic device or manual process” that monitors or copies the product | Do not build this. Enforcement is real and the workflow is a liability. |
| Scraping without a license | Bots harvest listing pages directly | Prohibited, and the subject of CoStar litigation and settlements | Not a gray area. Walk away from vendors pitching it. |
| In-license exports, AI downstream | A licensed analyst uses the product’s own export features; AI normalizes and analyzes the firm’s copies | Uses the product as shipped; confirm caps and permitted use in your license schedule | The recommended pattern. All the analytical leverage, none of the exposure. |
| Licensed feeds and alternatives | Data licensed for programmatic use: Yardi Matrix through its Claude connector, public records, broker-shared comps | Governed by each source’s own commercial terms | The complement for market data, and the only path that scales portfolio-wide. |
What stays human, and the honest cautions
The operator read
Finish with the judgment call.
The reported facts are above. Enter your email for PSV's operator conclusion and a year of access to every newsroom brief.
Free. No card. Privacy policy. Unsubscribe anytime.
by PSVLiveBuild the workflow behind this analysis. Train with the operators doing it.
Real deal files, live builds, and production-ready CRE AI workflows inside the CRE AI Institute.
Clear answers
Common questions about can AI access CoStar data
Does CoStar have an API for AI tools?
No public self-serve API exists for CoStar Suite, LoopNet listing data, or CoStar’s comps and analytics products as of this writing, and access beyond the logged-in portal runs through commercial conversations with CoStar. CoStar’s Terms of Use prohibit licensees, without express written permission, from using any data mining, gathering or extraction tool, or any robot, spider or other automatic device or manual process, to monitor or copy any portion of the product. That language reaches browser automation that drives the logged-in portal, not just traditional scrapers. CoStar also enforces its terms: in 2016 the company announced a settlement in which RealMassive paid $1 million over what CoStar described as systematic misappropriation of its research.
What is the legal way to use CoStar data in an AI workflow?
Work downstream of the product. A licensed analyst uses CoStar’s own export features in the ordinary course of work, subject to the caps and permitted uses in the firm’s license schedule, and the firm’s AI reads the firm’s copies after they leave the portal: normalizing exported records into one schema, deduplicating against the existing pipeline, applying buy-box criteria with arithmetic done in code, and producing a shortlist memo traced to each export file and date. The AI never touches CoStar’s systems and writes nothing back. Confirm your license schedule with your CoStar representative and counsel before building, because schedules differ by agreement and terms change.
What are licensed alternatives to CoStar data for AI workflows?
For market data, Yardi Matrix publishes a connector on Anthropic’s marketplace that brings its data directly into Claude under Yardi’s own commercial terms, announced June 17, 2026. Public records, broker-shared comps, and data the firm exports from its own systems of record round out the stack. The question to ask any vendor claiming CRE data coverage is where the data comes from and under what license: sources that answer plainly, their own licensed dataset, public records, or customer-exported files, can support a production workflow. Tools that deliver CoStar integration by driving the portal with a bot, sometimes with the customer’s own credentials, transfer license risk to the licensee.
Primary sources and operating references
These references support the control, research, and operating standards used in this guide. PSV’s workflow recommendations are original analysis.
- CoStar Terms of Use, license agreement clauses on data mining, extraction tools, robots, spiders, and automatic or manual copying (accessed August 16, 2026)
- CoStar Group press release: CoStar Halts RealMassive’s Systematic Theft Practices, Receiving $1M Payment (2016)
- Yardi press release: Yardi publishes second connector on Anthropic marketplace, bringing Yardi Matrix data to Claude (June 17, 2026)
Topics
Related PSV analysis
CRE PROPTECH NEWS
Claude Talks to Yardi Now. Most Operators Haven’t Caught Up.
Does Claude integrate with Yardi? It is one of the most common questions in PSV client scoping calls and Institute office hours, and the answer changed while most of the industry was not looking. Yardi announced Virtuoso Connectors in September 2025, and by June 2026 it had published two MCP connectors on Anthropic’s marketplace: live Yardi operational data and Yardi Matrix market data, both readable from inside Claude.
AI TOOL SELECTION
The Best AI Tools for Commercial Real Estate: A Vendor-Neutral Selection Framework
How a CRE team should choose models, document workspaces, data sources, automation, and control layers without buying overlapping software or outsourcing its operating knowledge.
UNDERWRITING
AI Underwriting for Commercial Real Estate: A Source-Cited Workflow
How to use AI to normalize a rent roll and T-12, prepare a first-pass underwriting, and accelerate IC work while keeping calculations, assumptions, and approvals reviewable.
Related guides
Cornerstone PSV guides on the workflows in this article.
Claude vs ChatGPT for CRE
An operator's comparison of Claude and ChatGPT for commercial real estate underwriting, and why the grounded setup matters more than the model brand.
Read the guideClaude MCP for CRE
MCP explained for CRE teams: connect Claude to the files and systems you already run so answers come from your data, with citations.
Read the guideClaude for CRE Operators
The five shifts AI-native CRE shops made: how operators run their work with AI, grounded in real deals and templates.
Read the guide
by PSVLiveYou read the operator view. Now learn to run the workflow.
The AI MBA for commercial real estate: the workflows these briefs describe, taught end to end on real deal files, with live builds and a community of CRE operators.





