---
name: liquidity-research-brief
description: Build or compare a dated trading research brief connecting Undertow Bitcoin exit estimates, Seiche funding evidence and an optional covered institution's LiquiLens disclosures. Use for repeat research and source changes, not trading signals or automated orders.
---

# Liquidity research brief

Use the reviewed Python sources in the Undertow crypto kit at
https://liquilens-undertow.com/crypto/. Keep `crypto_brief.py` and
`financial_research.py` together after extraction.

`python3 crypto_brief.py doctor --verification` checks the three MCP services
and required tools without making research calls. Use `--verification` for
operator tests; do not count them as customer adoption.

For a caller-requested brief:

```sh
python3 crypto_brief.py run --size-usd 100000 > first.json
python3 crypto_brief.py run --size-usd 100000 --previous first.json > next.json
```

Supported CLI sizes are the four published examples: 1000, 10000, 100000 and
1000000 USD. Use `crypto_exit_check` directly for other research sizes.
Add `--slug` only for a specific institution. The client resolves exact
LiquiLens coverage before requesting that review; it never substitutes a
similarly named bank. Without a named institution, the brief has funding and
exit sections only. Discover institution slugs through LiquiLens's
`banking_specialisation_coverage`; registry presence alone is not a dossier.

The brief carries separate source evidence, source dates and eligibility for:

- Seiche: `https://api.seiche.info/mcp`, `money_market_context`.
- Undertow: `https://api.seiche.info/undertow/mcp`, `crypto_exit_check`.
- LiquiLens: `https://api.liquilens.in/mcp`, exact institution coverage/review.

Exit code 2 means partial evidence: preserve available sections and report
missing ones. A transport failure or withheld score is not calm. Compare
only the same request; differences include source clocks, revisions and
coverage changes, not necessarily market moves. Use `--format markdown` for
a readable export. JSON is written only to stdout unless redirected.

The command runs once. Schedule it only when the user asks and specifies a
cadence. Preserve source rights and restrictions. No common risk score,
execution authority, credit approval or account integration is created.
