Executive Summary: Manufacturers are asset-heavy and contract-dependent, which means their litigation record carries information that financial statements alone do not surface. A breach of contract suit naming a top customer is a revenue concentration event before it is a legal event, and a mechanics lien or environmental order can quietly encumber the very collateral you are advancing against. This guide covers which manufacturer case types matter to credit, how to read counterparty names as concentration signals, and where automated court data currently stops. Cobalt Intelligence covers New York State and Miami-Dade County, Florida only, and that limit is stated plainly throughout.
Why does a manufacturer's litigation profile read differently than a service business?
A staffing agency that gets sued has a dispute. A machine shop that gets sued may have a dispute, a stalled receivable, a threatened supply relationship, and a lien on the CNC equipment your loan is secured by. The difference is structural. Manufacturers carry hard assets, work under long-dated purchase agreements, and sit inside supply chains where one counterparty failure propagates.
The macro picture matters here because it sets your base rate. The ISM Manufacturing PMI registered 53.3% in June 2026, a sixth consecutive month of expansion after ten months of contraction, with 14 of 17 subsectors reporting growth.[1] Expansion is not the same as comfort. In the National Association of Manufacturers Q2 2026 Outlook Survey, raw material costs jumped to the top business challenge at 83.1%, up 25.6 percentage points from 57.5% in Q1, with trade uncertainty second at 71.8%.[2] Growing revenue against rising input costs is exactly the condition that produces contract disputes: someone has to absorb the delta, and the purchase order rarely says who.
What does asset-heaviness change about your collateral analysis?
Equipment finance sits underneath most manufacturer balance sheets. The Equipment Leasing and Finance Association reported June 2026 new business volume of $10.5 billion, a delinquency rate of 1.7% over 30 days, and a loss rate of 0.54%, with ELFA President and CEO Leigh Lytle noting that "financial conditions remain healthy."[3] Healthy aggregate performance says nothing about the applicant in front of you. It does tell you that a manufacturer applying to an alternative lender at a higher cost of capital has usually already been through the equipment finance channel, which means the equipment is probably already pledged.
Why does contract dependence make litigation a revenue signal?
A manufacturer's revenue arrives through a small number of named purchase agreements. When one of those agreements breaks, it produces a court filing with the counterparty's name on it. That name is the piece of information the financial statements are least likely to give you. Academic work on this is direct: suppliers that depend on at least one major corporate customer carry 5.0% to 6.0% higher borrowing costs on bank debt and 7.0% to 9.9% higher costs on public bonds, because concentration raises the cost of both equity and debt capital.[4] The credit market already prices concentration. Court records are one of the few places a private-company underwriter can observe it.
What does a breach of contract suit actually tell you about revenue concentration?
This is the distinctive read for this vertical, and it is worth stating carefully. Under U.S. GAAP, public companies must disclose any single customer representing 10% or more of revenue, which is the accounting profession's marker for where ordinary business risk becomes a material disclosure event. Private manufacturers have no such obligation, and the applicants you underwrite are almost entirely private.
So you are left inferring concentration. A contract dispute gives you an inference the financials cannot. When Acme Stamping sues Regional Truck Bodies for $1.4 million on an open account, you have learned that Regional Truck Bodies was a large enough customer to generate $1.4 million of unpaid invoices, and you have learned it without the applicant volunteering anything.
How do you distinguish a plaintiff-side suit from a defendant-side suit?
The direction changes the meaning entirely.
• Applicant as plaintiff on an account. The manufacturer is chasing money it already earned. The credit read is a collection problem and a working capital gap, plus a concentration disclosure if the sued customer is large relative to stated revenue.
• Applicant as defendant on delivery or quality. A customer is refusing to pay because the goods were late, wrong, or defective. This threatens future orders from that customer, not just the disputed invoice.
• Applicant as defendant on a supplier claim. An input vendor is suing for nonpayment, which is a liquidity signal that usually predates any bank covenant breach.
• Applicant as plaintiff against a supplier. Often an input shortage or a quality failure that disrupted production. Read this alongside the applicant's own delivery performance.
• Cross-claims between the same two parties. A relationship in structural breakdown. If the counterparty is a top customer, the revenue at risk is the whole account, not the disputed amount.
Commercial counsel expect more of this. Contract disputes have long been among the most common sources of commercial litigation, and 2026 conditions of tighter budgets, shifting vendor relationships, and continued supply chain inconsistency are pushing volumes higher.[5]
What do you do once you have the counterparty name?
Run the counterparty. This is the step most underwriting teams skip. If a manufacturer applicant is suing a customer for a sum that looks material against stated revenue, the counterparty's own entity status, standing, and litigation record become part of your credit file. A judgment against a customer that is itself administratively dissolved is not a receivable, it is a write-off waiting for an accountant. Our guide to civil court filings as early warning signals for portfolio risk walks through the timing of these signals in more depth.
Which case types matter most when you are lending to a manufacturer?
Not every filing is a credit event. Manufacturers generate routine litigation that has nothing to do with repayment capacity. The categories below are the ones that move a decision.
• Breach of contract with a named customer. The concentration signal described above. Highest information value per filing.
• Product liability and warranty claims. Verdict exposure has moved sharply. Marathon Strategies counted 135 nuclear verdicts above $10 million in 2024, a 52% increase over 2023, totaling $31.3 billion, with the median verdict rising to $51 million from $44 million in 2023 and $21 million in 2020.[6] Products liability led the categories driving that record, and 49 verdicts crossed $100 million.[7]
• Mechanics and materialmen liens. A supplier or fabricator that delivered material and was not paid can attach a lien. For manufacturers doing project or construction-adjacent work, these liens sit directly on the assets and receivables you may be counting.
• Supplier and vendor disputes. Input cost and supply chain stress showing up in the docket before it shows up in the P&L.
• Environmental and regulatory actions. These can encumber real property. EPA secured roughly $714.3 million in FY 2025 commitments from responsible and third parties for site cleanup and recovered more than $174.1 million for past costs, obtaining enforcement instruments at 55 Superfund sites.[8] A manufacturer named as a responsible party has an obligation that competes with your loan.
• Employment and wage claims in volume. A single claim is noise. A pattern across a short window is an operational and cash management signal.
• Prior judgment enforcement actions. Someone already won and is now trying to collect, which puts them ahead of you in practice if not in priority.
How should product liability change your advance rate?
Product liability is the manufacturer risk that is least visible in a bank statement review and least correlated with recent revenue. A pending claim with a plausible path to a large award is a contingent liability that no cash flow model captures. You are not expected to value the claim. You are expected to know it exists, size it roughly against the applicant's stated insurance, and decide whether the term of your advance clears the likely resolution window.
What makes environmental actions different from other litigation?
Because they can attach to real property, environmental matters change what your collateral is worth in a liquidation, not just what your borrower's cash flow looks like. If you are lending against a facility or taking a mortgage position, a named party in an ongoing cleanup action is a different credit than the financials suggest. Regulatory change alerts, including tariffs, changes in law, environmental regulation, and bans, rose 128% year over year in Resilinc's 2024 disruption data.[9] The regulatory surface manufacturers operate on is expanding, not contracting.
How do liens and encumbrances stack against equipment you are lending against?
Assume the equipment is already pledged. That is the correct starting posture for a manufacturer applicant coming to an alternative lender.
Article 9 of the Uniform Commercial Code governs security interests in personal property including inventory, equipment, and receivables, and priority among perfected secured creditors generally follows first in time, first in right, subject to purchase money security interest rules that can override the filing order.[10] Equipment filings frequently describe collateral by reference to an attachment listing make, model, and serial number, and that attachment must be filed with the financing statement to be effective.[11]
Why is a court check incomplete without a UCC check for this vertical?
Court records tell you who is fighting. UCC filings tell you who already holds the asset. For manufacturers those are different populations, and either one alone gives you a false picture.
A judgment creditor who has won but not yet perfected sits behind a blanket lienholder who filed three years earlier. A mechanics lien on specific equipment may sit ahead of a general blanket filing depending on state law and timing. Run court records without UCC and you will over-weight a $200,000 judgment while under-weighting the $2 million blanket filing that actually determines your recovery. Our post on how UCC liens reveal hidden encumbrances in business loans covers the mechanics of reading those filings.
What does the current credit environment do to this calculation?
Banks reported tighter standards on commercial and industrial loans to firms of all sizes over the first quarter of 2026, with demand basically unchanged, in the April 2026 Senior Loan Officer Opinion Survey.[12] Standards had already tightened through the prior quarter.[13] Tighter bank standards push manufacturers toward alternative and specialty capital, which means the applicant pool arriving at your desk includes borrowers who were declined upstream for reasons the application will not explain. Chapter 11 filings hit a decade high in 2025, and industrials were part of the concentration that drove it.[14]
"Are there any open liens against them? Any litigations associated to this specific contractor?"
Peter Chong, Highwire, describing the pre-qualification questions his platform has to answer before work begins.
What are your options for pulling manufacturer court records today?
Before getting to any specific API, it is worth being honest about the landscape, because most underwriting teams already have a partial answer in place.
PACER covers federal courts. That is useful for bankruptcy, patent, and diversity cases, but the majority of contract, lien, and collection actions against private manufacturers are filed in state court, so federal-only coverage misses the case types most relevant to credit.
Unicourt and similar aggregators offer broad state and county coverage with normalized data. Breadth is their advantage. The tradeoff is usually cost per pull at volume and the work of reconciling records to your own entity keys.
LexisNexis, CSC, and Wolters Kluwer serve legal and corporate services markets with deep research tooling. They are built for attorneys and corporate secretaries, not for a decisioning pipeline that needs a structured answer in under two minutes.
Manual courthouse or clerk portal search is accurate and slow, and it does not scale past a certain application volume.
The gap most teams describe is not coverage and it is not accuracy. It is integration friction: getting a structured, machine-readable court answer into the same workflow that already holds the entity check, the UCC pull, and the bank data, without a person opening a browser tab. That is the specific problem Cobalt built for, and the honest framing is that Cobalt solves it narrowly rather than broadly.
How does the Cobalt Court Records API fit into a manufacturer underwriting stack?
State the limit first, because it determines whether the rest of this section is useful to you. The Cobalt Court Records API covers New York State and Miami-Dade County, Florida. That is the entire coverage footprint. It is not national, it is not federal, and it does not include PACER.
The reason is demand, not ambition. Roughly 80% of Cobalt's funder customers file judgments in exactly those two venues. New York has long been the center of alternative lending, and Miami-Dade became the second hub after a large migration of funders to South Florida. Coverage was built where the customers already were. Broader jurisdictions are on the roadmap, including a planned human-assisted queue for unsupported jurisdictions that would run slower, on the order of an hour, and has not shipped.
If your manufacturer book is concentrated in the Midwest or the Southeast outside Miami-Dade, this product will not serve you today. Lara Hodgson of RoxWrite put the objection plainly in a demo: "Most of our clients are not in New York." Cameron Kelliher of Elementix reached the same conclusion: "We'll stay away from the court stuff then. I wish the court stuff was rounded." Those are fair reads, and they are the right decision for those books.
What does the API call actually look like?
The endpoint is asynchronous only. You pass a callback URL, Cobalt pulls live from the court site, and the result posts back to you when the search completes, typically in 30 to 120 seconds. There is no synchronous mode.
curl -X GET "https://apigateway.cobaltintelligence.com/courtCases?businessName=Precision%20Metalworks%20LLC&jurisdiction=newYork&callbackUrl=https%3A%2F%2Fyour-app.example.com%2Fwebhooks%2Fcourt" \
-H "x-api-key: YOUR_API_KEY"Valid `jurisdiction` values are `newYork`, `miamiDade`, `testNewYork`, and `testMiamiDade`. The two test values run the full request path without consuming credits, which is how you should build and regression-test the integration before pointing it at production traffic. Pricing is one credit per lookup, the same as a Secretary of State pull. Returns include judgment details, case number, case type and division, filing dates, party names, and amounts where the underlying record includes them. Not every record carries an amount.
The party names are the field that matters most for this vertical. That is where the concentration signal lives.
Where does this sit in the verification order?
Court records are a layer, not a decision. The sequence that works for manufacturers is Secretary of State first to confirm the entity exists and is in good standing, then UCC to establish who already holds the equipment, then court records to find disputes and judgments, then TIN or EIN verification to confirm tax identity. Cobalt is a data source, not a decisioning engine. It returns records. Your credit policy decides what they mean.
New York is worth calling out specifically for manufacturers. It is the only state where Cobalt's SOS, UCC, contractor license, and court records coverage all overlap. If you write New York manufacturing paper, you can assemble the full stack from one integration. Outside New York the stack fragments, and you should plan for that rather than discover it in production.
Evaluating whether court data belongs in your manufacturer underwriting flow? Request a Cobalt Intelligence demo and test the New York and Miami-Dade coverage against a real sample of your own applications before you commit to anything.
What does a practical manufacturer court check workflow look like?
The teams getting value from court data are not running it on everything, and they are not running it manually on nothing. They are triaging.
Yehudah Aron of Cucumber Capital framed the economics directly: "If courts are cheap enough, then it's worth it to run on every [application] automatically." At one credit per lookup, that math works for many books. Anthony at CorFinGroup, running 50 to 60 submissions a day with 10 to 15 deep dives, described wanting "one cost effective solution for KYC and KYB" rather than a stack of separate vendor logins.
The alternative is what most shops actually do, which Max Weisz of an MCA operation described as running "New York court separately and then we run Unicourt, and then we run UCC searches" across roughly 500 files a day. Three tools, three logins, three reconciliation steps, per file.
What should trigger a court pull versus a full deep dive?
• Always pull when the deal size crosses your manual review threshold and the applicant is domiciled or operating in a covered jurisdiction.
• Always pull when the applicant is asset-based and your advance is secured by equipment or receivables.
• Escalate to a manual read when a returned case names a counterparty that appears in the applicant's stated top customers.
• Escalate when the case type is product liability, environmental, or lien, regardless of the stated amount.
• Escalate when there are three or more open matters, because volume is more predictive than any single amount.
• Deprioritize routine employment matters, small claims, and closed cases older than your look-back window unless they show a pattern.
How do you handle the async callback in a real pipeline?
Treat the court pull as a parallel enrichment, not a blocking gate. Fire the request when the application is received, continue running the checks that return synchronously, and reconcile the callback against the file when it lands. A 30 to 120 second wait is invisible if it runs alongside your other pulls and disqualifying if it runs in sequence in front of an underwriter who is waiting. Berkman Financial's ask was exactly this shape: applications run automatically through Salesforce rather than pulled by hand.
Where does court data stop being useful for manufacturer credit?
Honesty about the limits is what makes the capability claims worth believing.
Court records are a lagging indicator of a dispute and a leading indicator of a loss. A filing means the parties already failed to resolve something privately, usually months after the commercial relationship broke. You will not see the customer who quietly stopped ordering, only the one who stopped paying and got sued.
Coverage is the harder limit. A clean New York court result on a manufacturer with plants in Ohio and Alabama tells you about New York. It does not tell you the applicant is clean, and no underwriting memo should say it does. Gate Rock Capital's read was that state index coverage on court search was worth paying meaningfully more for, which is a fair statement of where the value concentrates.
Amounts are also inconsistent, because the underlying court record does not always publish one. And court records do not cover bankruptcy filings, which are federal. Our post on how court records reveal bankruptcy risk before funding covers what state court data can and cannot tell you ahead of a federal filing.
The right conclusion for most manufacturer lenders is narrow and useful: if your book has meaningful New York or Miami-Dade exposure, court data at one credit per lookup is cheap enough to run broadly, and the counterparty names it returns are information you cannot get anywhere else. If your book does not, wait for broader coverage rather than paying for a check that will come back empty for structural reasons.
.jpg){kind=small}
.png)