In 2026, a 300-megawatt AI data center deal was announced, helped support a public company's stock, and was later alleged by a short seller to trace back to a single-family home. To verify a data center counterparty can actually deliver before you sign, confirm in writing that it has built comparable megawatts before, that it owns or controls the land, the building, and the power and that none of them carry prior liens, that its named partners confirm the relationship, and that its financing is documented rather than asserted. A signed contract does not make an unbuildable project buildable.

This is a practical guide for data centers and neoclouds signing high-value capacity, cooling, construction, and interconnection agreements in the AI buildout. It covers the diligence that catches a counterparty who cannot deliver, and the contract terms that protect you if you sign one anyway.

The data center counterparty diligence checklist: verify ownership and search for prior claims at every layer

Counterparty diligence runs across the whole stack, the entity, the land, the building shell, and the power, and at each layer you confirm two separate things: who actually owns or controls the asset, and who else already holds a claim against it. A claim you miss is capacity a creditor can pull out from under you after you sign. Each item below is answered by a document or a public-record search, not an assurance.

  • The entity and its track record. Confirm the operating company is real and has energized comparable megawatts before. Verify the entity, its principals, and named prior projects, not a client logo wall.
  • Land title. Confirm who owns the parcel through a title search or title commitment. Verify the counterparty holds the deed, a recorded lease, or a recorded option on the specific site, not a map with a pin on it.
  • Liens and mortgages on the land and the building. Search the real-property records for recorded mortgages, construction and mechanic's liens, tax liens, and easements against the site and the shell. A prior lienholder can foreclose on the ground the project stands on.
  • The power stack, and the security interests against it. Confirm the interconnection agreement is executed, with a utility queue position and an energization date, and confirm the power purchase agreement (PPA) that feeds the campus. Then search for security interests, collateral assignments, and lender step-in rights against the power agreements themselves. A PPA or interconnection right can be pledged as collateral, and if the counterparty defaults, its creditors can enforce against that contract and take the capacity you were counting on.
  • UCC-1 and PPSA filings against the counterparty. Search UCC-1 filings (PPSA in Ontario, Canada) for blanket liens over all assets. If a lender already holds a security interest in everything the counterparty owns, including its contracts and receivables, your deal sits behind that lender.
  • Financing. Confirm the capital is committed with signed term sheets or closed rounds, then reconcile it against what is already pledged. Committed funding sitting behind a blanket lien is not free capital.
  • Named partners and vendors. Confirm every named vendor and strategic partner acknowledges the relationship in writing when you contact them directly.
  • Physics. Sanity-check the claimed capacity, power draw, water use, and build timeline against what the grid and the laws of physics actually allow.

The rest of this guide expands these into the specific red flags that answer them, using the Innventure matter as an attributed example, then into the contract terms that protect you if a counterparty clears diligence and still fails to deliver.

The compute boom rewards counterparties who overpromise capacity, the same way oil, real estate, and crypto did

Fast money attracts operators who cannot deliver, and the AI compute buildout is moving faster than any of them. The pattern is old. Oil, commercial real estate, biotech, and crypto each pulled in a wave of promoters whose decks outran their capabilities, and diligence was the only thing separating a real counterparty from a name on a term sheet.

The scale of the current cycle is what makes the exposure larger, not different. Quinn Emanuel counted more than $120 billion in data center spending moved off corporate balance sheets in roughly eighteen months, much of it through special-purpose vehicles that are hard to see into. Demand looks bottomless in part because it is circular: the same alert notes OpenAI has committed to buy roughly $300 billion in compute from Oracle, $38 billion from Amazon, and $22 billion from CoreWeave, arrangements the firm compares to the vendor financing of the dot-com era. When one counterparty's promise anchors another's revenue model, a single failure to deliver travels.

For a data center or neocloud buyer, that is the commercial reality to price in. The projects are real, the capital is real, and so are the counterparties who will sign a 300-megawatt agreement they have no way to fulfill. Diligence and contract structure are how you capture the upside of this market while staying on the right side of the deals that unravel.

The Innventure "300MW" case shows how far a data center claim can travel before anyone checks it

The Innventure matter is a public example of a capacity claim that moved real money before it was verified. This account is drawn from public filings, a short-seller report, and securities litigation. The allegations are contested and have not been proven in court.

Innventure, Inc. (NASDAQ: INV) is a technology commercialization company whose subsidiary Accelsius makes direct-to-chip liquid cooling. According to the securities class action complaints, Innventure repeatedly highlighted an Accelsius agreement with a counterparty called DarkNX to deploy cooling across a new 300-megawatt AI data center campus in Ontario, and used that agreement to support expectations of substantial revenue growth. On May 28, 2026, Morpheus Research published a report alleging the DarkNX venture was fabricated, stating there was "zero evidence" the project existed or that DarkNX had the team or funding to pursue it. Morpheus is a short seller and discloses a position that profits if the stock falls, so its report is an interested source, not a neutral finding.

What followed is a matter of record. The deal was later cancelled, Innventure shares fell 55%, and multiple securities fraud class actions were filed against Innventure and certain executives, pending in the Southern District of New York. The defendant is Innventure, not the buyers who might have contracted with the counterparty. The lesson for a buyer is upstream of the lawsuit: the checks below are the ones that catch this before you are the one holding the agreement.

The red flags that separate a real data center operator from a slide deck

The strongest diligence red flag is a claim that cannot be independently confirmed from a primary source. Announcements, decks, and websites are assertions. Diligence is the work of matching each assertion to a document, a public record, or a third party who confirms it directly. The checks below are general practice; each is paired with what Morpheus alleged in the Innventure matter to show what the check is designed to catch.

  • No comparable build history. Ask for named, verifiable projects the counterparty has energized at similar scale. Morpheus alleged the counterparty had roughly nine employees, none with data center experience, and a founder with no record of building or operating data centers.
  • A registered address that is not an operating site. Confirm the headquarters and the project site through property and corporate records. Morpheus alleged the company was registered to a family home in suburban Toronto and listed an operating address that was a trucking terminal, with the tenant denying any shared space.
  • A company that is younger than the deal it announced. Check the incorporation date against the scope. Morpheus alleged the counterparty was incorporated on November 22, 2024, about twelve months before a multibillion-dollar project announcement.
  • Named partners who will not confirm the relationship. Call every vendor and strategic partner named and get confirmation in writing. Morpheus reported that Dell, Supermicro, and Schneider Electric each said they had no such partnership or relationship when contacted.
  • Assets that are pledged out from under the deal. Search UCC-1 and PPSA filings and the real-property records for liens, mortgages, and collateral assignments against the land, the building, and the power agreements. A counterparty can hold a signed PPA that its lender is entitled to seize on default, so an unencumbered-looking deal can still sit behind someone else's security interest.
  • Financing that is asserted, not documented. Ask for signed term sheets, closed rounds, or lender commitments, and search public lien and security-interest registries. Morpheus alleged it found "zero signs" of institutional funding and no registered liens for a project described as needing more than $3 billion.
  • Capacity figures that fail a physics check. Sanity-test the headline numbers against what the grid can supply. Morpheus noted the counterparty's site claimed 998 GW of capacity, which it observed would require roughly three-quarters of all US electricity.
  • No power and no land secured. Require the signed interconnection agreement, the utility queue position, and the site control documents. A 300-megawatt campus with no visible grid connection or land rights is a plan, not a project.
  • No independent coverage or references. A genuine hyperscale campus generates permitting filings, local reporting, and utility records. Silence around a project of that size is itself a signal.

None of these checks requires litigation or subpoena power. They require calling the named parties, pulling the public records, and refusing to accept an assertion in place of a document.

Why a lien on the power contract can cost you the capacity, not just the counterparty

The encumbrance that catches buyers off guard is a security interest against the power agreement itself. A signed PPA or interconnection right is a valuable, assignable asset, and counterparties routinely pledge it as collateral to raise construction financing. That creates two exposures for you. First, if the counterparty defaults on that financing, the lender can enforce its collateral assignment, step into the contract, or terminate it, and the capacity you contracted for goes with it. Second, many PPAs and interconnection agreements already contain collateral-assignment and lender step-in provisions that, by their own terms, put a financier's rights ahead of yours.

So the power diligence has three parts, not one. Confirm the agreement is executed and the capacity is real. Search UCC-1 filings (PPSA in Ontario, Canada) for security interests against the power agreement and the counterparty's contract rights. Read the assignment and step-in clauses inside the agreement, and confirm whether any lender consent is required for the counterparty to perform for you. Title to the land and the building is table stakes. The power contract is the asset most likely to be quietly encumbered, and the one whose loss kills the deal.

What 300 MW actually is, and why the number alone should have prompted scrutiny

Translating a capacity figure into operating units is often the fastest diligence check available. 300 megawatts is hyperscale territory, not a starter facility. At roughly 1.3 kilowatts of all-in facility power per high-end AI GPU, 300 megawatts is enough to run on the order of 200,000 top-tier accelerators, with the exact number depending on cooling and overhead. That is a campus in the class of a major utility's largest single customers, and it requires a grid connection that, in constrained markets, can take years to secure.

That framing turns the capacity claim into a set of answerable questions. Where is the substation? What is the interconnection queue position and expected energization date? Who is the utility, and will it confirm the load? A counterparty that can build 300 megawatts can answer these in documents. A counterparty that cannot will offer a target date and a press release. Doing the unit math first tells you which conversation you are in.

The contract terms that protect you when a counterparty cannot deliver

The contract's job is to move the risk of non-delivery back onto the party who controls it. Even with clean diligence, projects in this market slip for reasons the counterparty may not disclose. Bain has warned that equipment lead times now stretch eight to twenty-four months, utility interconnection can take up to five years, and financings underwritten on "booked-but-not-billing" terms count revenue that has not actually arrived. Five terms carry most of the protection.

  1. An unconditional capacity commitment with a hard date. Draft the difference between "capacity is expected by a date" and "the counterparty is obligated to deliver a specified number of megawatts by a specified date." As a National Law Review analysis of these deals puts it, contracts should clarify whether a commitment is an estimate or an enforceable obligation, and should spell out the conditions precedent and regulatory dependencies attached to it.
  2. Milestone-gated payments. Tie money to verified progress rather than to the calendar or the signing. Payments released against permits filed, interconnection secured, and equipment delivered protect you from the "booked-but-not-billing" pattern, where cash leaves your side against capacity that never materializes.
  3. Representations you can sue on, plus a lien-free warranty. Have the counterparty represent and warrant the load-bearing facts: that it holds site control, that its interconnection is at a stated queue position, that its financing is committed, that its named partners are under contract, and that the land, building, and power agreements are free of liens and collateral assignments except as disclosed. A representation converts a sales claim into a term with a remedy behind it, and a lien-free warranty backstops the searches you ran in diligence.
  4. A termination right triggered by a defined delay, with your money back. Set a clear outside date and a right to walk if it is missed, backed by liquidated damages, a deposit held in escrow, or a return of prepayments. Quinn Emanuel notes real deals turn on exactly this mechanic, citing a structure where a counterparty could terminate if construction ran more than 180 days past the target completion date. The delay threshold and the remedy are the negotiation.
  5. Concentration and cross-default protection. Avoid letting a single counterparty's promise anchor your revenue model, and understand how a default on one facility can cascade across linked obligations. In a market Quinn Emanuel describes as full of circular, take-or-pay commitments, knowing who else depends on your counterparty's performance is part of pricing the deal.

Force majeure scope, notice-and-cure periods, and audit and inspection rights round out the structure. The point of all of it is the same: a counterparty who intends to deliver will accept commitments, milestones, and remedies tied to delivery. One who resists every enforceable obligation is telling you something diligence may not have surfaced yet.

Frequently asked questions

What is counterparty due diligence for a data center deal? Counterparty due diligence for a data center deal is the process of verifying, before signing, that the party on the other side owns or controls what it promised and that no one else has a prior claim on it: the entity, the land, the building, the power agreements, and its financing. It tests documented facts and public-record searches, not slides or announcements.

How do you verify a data center developer can deliver the power it promised? Ask for the signed interconnection agreement and power purchase agreement, the utility queue position, and the expected energization date. Then search UCC-1 (or PPSA in Canada) filings for security interests against those contracts and read their collateral-assignment and lender step-in clauses. A power agreement that is pledged to a lender can be lost to that lender's default remedies even if it is signed.

Can a data center's power agreement be taken by its creditors? Yes. A power purchase agreement or interconnection right is a valuable, assignable asset that counterparties routinely pledge as collateral to raise financing. If the counterparty defaults on that financing, its lender can enforce a collateral assignment, step into the contract, or terminate it, and the capacity you contracted for goes with it. This is why diligence searches UCC-1 or PPSA filings against the power agreements, not just the land and building.

What contract terms protect you if a data center counterparty misses its deadline? Milestone-gated payments, an unconditional capacity commitment with a hard delivery date, representations you can sue on, a termination right triggered by a defined delay, and liquidated damages or an escrow that returns your money. Together these move the risk of non-delivery back onto the party who controls it.

Is a signed LOI or MOU a binding commitment to deliver capacity? Usually no. Most letters of intent and memoranda of understanding are expressly non-binding as to performance. Treating an LOI or MOU as a firm capacity commitment is a common and expensive mistake. Only an executed agreement with a defined obligation, a delivery date, and a remedy binds the counterparty to deliver.

What is a physics check in data center counterparty diligence? A physics check tests whether a counterparty's headline numbers are even possible before you engage on price. Compare the claimed capacity, power draw, water use, and build timeline against grid availability and known engineering limits. A 300-megawatt campus needs a grid connection that can take years to secure, so a claim with no interconnection behind it fails the check. In the Innventure matter, Morpheus noted a site claiming 998 GW of capacity, which it observed would require roughly three-quarters of all US electricity, a figure a basic physics check flags immediately.

Build the diligence and the contract terms into the deal, not after it

The counterparties who cannot deliver are the cost of a boom this large, and they will keep signing agreements as long as the market moves this fast. The protection is diligence that checks every claim against a primary source and a contract that makes delivery an obligation with a remedy behind it.

LegalLayer drafts, negotiates, and reviews high-value enterprise and infrastructure agreements, with a licensed lawyer accountable for the work. It adds lawyer-led negotiation with counterparties and legal agents tailored to how your deal team operates, so capacity, cooling, and interconnection contracts get the diligence and the terms above before you sign. If you are evaluating a data center counterparty, start with LegalLayer at legallayer.ai.

This article is general information, not legal advice. For advice on a specific transaction, consult a qualified attorney.

Sources