Underwrite · PCT-010 · Sourced card
Scan agreements for LME trapdoors
Scans every credit agreement in a book for liability-management trapdoors (unrestricted-subsidiary transfers, non-pro-rata uptiers, guarantor releases) and lists the blockers each one has.
Today vs automated
- Open 40 agreementsAssociate · manual
- Search for each blockerAssociate · manual
- Log results in a sheetVP / counsel · manual, re-keying
- Email / meeting hand-offAssociate → VP / counsel
- A new or amended credit agreement is loadedTrigger: starts on its own
- Extract key clausesAutomated · Document parser
- Check each blockerAutomated · LLM
- Rank the bookAI draft, human review · Model template
- Legal interpretationApprove / override · VP / counsel
AutomatedAI draft, human reviewHuman onlyTools: Data room, Document parser, LLM, Model template
Estimated valueestimate
80–1,100 analyst hours a year
$12k–$275k of time, vs an assumed $20k–$100k tool cost
Net: −$88k to $255k a year net of tool cost; at the low end of the assumptions it does not cover the tool cost.
Assumptions
- 3–6 analyst hours per agreement today; 0.5–1 hours with an agent, including review
- 40–200 agreements a year for one team
- $150–250 per hour loaded cost
- Tool or build cost $20,000–100,000 a year (both)
Estimate, based on the assumptions shown; your numbers will differ. How we estimate
What else it can do for the team
- Re-run the matrix after each amendment
- Compare a new term sheet's protections with the book's norm
- List positions where a non-pro-rata buyback is permitted
- Draft the asks for the next amendment negotiation
- Feed results into the watchlist for names under stress
How you get thereFour steps from prompting to an agentic workflow; most teams start at step 4.
Needs: an approved AI tool, a confidentiality policy.
Risk: unchecked answers, data pasted outside policy.
Needs: field definitions, a template, document parsing.
Risk: breaks silently when formats change.
Needs: inbox/doc-store access, system write-back, logging.
Risk: acting on a misread; needs review gates.
The automated lane above
Needs: shared data model, permissions, audit trail, exception queue.
Risk: errors compound across steps; needs monitoring.
Typical starting point
Solution optionsBuy (10 vendors listed), build or hybrid, with the trade-offs of each.
Hebbia, Ontra, 9fin, Octus, Indus Valley Partners (IVP for Credit), Blueflame AI, Alphastream, CovenantIQ, CredCore, CreditBase
Fastest start; you adapt to the product's data model and pricing.
An LLM API, a document parser, a vector or document store, your data warehouse, and a review queue.
Fits your definitions exactly; you own maintenance and controls.
Vendor extraction feeding your own checks, templates and systems.
Common middle path; two things to integrate and govern.
Listing is not endorsement.
What changes for the team3–6 h → 0.5–1 h per agreement (estimate); coverage goes from the sections someone had time to read to every clause and schedule checked against the term sheet.
How it works
Full title: Lender-on-lender violence radar: scan every credit agreement for J.Crew, Serta, and Chewy trapdoors
“Three filed credit agreements. One has no Serta blocker. Here is the clause.”
Scenario
SAMPLE: A fund holds 40 names. After a peer was primed in a non-pro-rata uptier, the PM asks which of the fund's own agreements are open to the same move.
What the human still decides
Legal interpretation. The scan flags language, and counsel decides what it means.
Why it matters
Liability management risk and the spread of blocker provisions are a 2026 documentation trend.
What the record shows
Checked 2026-10-15.
A real scan of Viavi's October 2025 term loan found J.Crew blockers (no Material IP into unrestricted subs), a Serta-style subordination consent with an exception if every affected lender is offered its pro rata share, a Chewy guarantor-release fix, and non-pro-rata open-market purchases and Dutch auctions permitted. That last one is the route used in some uptiers. 'Material IP' is not quantified, so the blocker is narrower than the label.
Try it: prompt and data
For this credit agreement, state whether it contains (a) a J.Crew blocker, (b) a Serta blocker, (c) a Chewy blocker. Quote the operative language and section, or say 'not found'. Do not give a legal opinion.
Data
Public inputs only (SEC/EDGAR filings, published methodologies, public signals). Every figure is cited.
Who uses it, vendors and build
- Segments
- Direct lending, Special sits / distressed
- Who uses it
- Associate, Special sits analyst, Counsel
- Build
- Vendor + in-house
- In-house
- Clause extraction with a checklist + counsel-reviewed test set. Estimate: 2–4 weeks; needs legal review of the eval set.
- Last verified
- 2026-10-15
Vendors that claim this capability
- Alphastream: covenant-basket-extraction, covenant-benchmarking, legal-doc-comparison
- CreditBase: covenant-benchmarking, legal-doc-comparison
- Octus: covenant-benchmarking
- Ontra: legal-doc-comparison
- 9fin: covenant-basket-extraction
- 5 more vendors claim related capabilities. See all vendors for this stage →
Tags reflect each vendor's own public claims at the linked page (checked 2026-10-15). Not tested, ranked or endorsed.
Sources and related
- Viavi Solutions term loan credit agreement, EX-10.1 (filed 30 Oct 2025)
- Credit agreement scan demo (every row hand-read against the filing)
- Hebbia: partnership with Octus
- CredCore launches Credit Agents: legal, structural and financial agents that answer cross-discipline questions on a firm's own deal files
- Hebbia plugs Octus credit data in through the Octus MCP Connector
- Octus connects its credit intelligence to Harvey's legal agents through its MCP Connector
- Octus credit data and analysis now available inside Perplexity through a connector
Part of the deal lifecycle: stage 4 of 7, Documents.
Next step
Related use cases
Get new walk-throughs
Not investment advice. Names marked SAMPLE are fictional. Found an error? See the corrections log.