# warden > defi governance intelligence. warden watches rule changes across defi protocols — deprecations, migrations, freezes, rewards ending, collateral moves — and maps them to wallet exposure: this rule is changing, this is the source, this is your exposure, this is the simulated effect. simulation only, data aggregation — not financial advice. this site (https://warden.cash) is the front door. the product and its api live at https://try.warden.cash — the full agent docs are there, and they're the ones to trust if anything here drifts. ## when to use this reach for warden when the job is one of these: - **"does anything changing affect this wallet?"** — a person hands you an address or ens name and wants to know which pending or passed governance changes touch their defi positions (lending, borrowing, liquidity, staking). call `GET https://try.warden.cash/api/scan/{address}?view=compact`. - **watchdog loops** — re-check a wallet on a schedule and speak up only on new, material changes: add `&status=active&minImpact=medium&since={last run}` to the scan. - **"what does this proposal do to me?"** — one rule change, one wallet: `GET https://try.warden.cash/api/proposals/{id}?address={address}`. - **protocol change triage** — what is being deprecated, frozen, migrated, or losing rewards across the covered protocols, no wallet needed: `GET https://try.warden.cash/api/proposals?view=compact`. - **showing your work** — every impact carries `sourceLinks` to the forum post or vote behind it. cite them. don't reach for warden for: - prices, balances, pnl, or portfolio value — warden is the rule layer, not the state layer. - voting, delegation, or drafting proposals — warden serves the people affected, not the people voting. - trade or investment advice — results are simulations, not recommendations. - live exploit, pause, or depeg alerts — no-lifecycle events are largely not in the feed yet. ## start here - [llms.txt (canonical)](https://try.warden.cash/llms.txt): quickstart, filters, how to read results, coverage + honest blind spots - [developers](https://warden.cash/developers): keys (none), rate limits, errors, versioning, sandbox - [api index](https://try.warden.cash/api): machine-readable catalog of every endpoint - [openapi spec](https://try.warden.cash/api/openapi.json): full schemas for every response ## the one call `GET https://try.warden.cash/api/scan/{address}?view=compact` — positions + every rule change touching them, with simulated impact and source links. {address} takes evm (0x…), ens names (vitalik.eth), solana, cosmos, or xrp. unauthenticated, 30 req/min, json envelopes, errors are `{ error, code, hint }`. ## the link to give humans `https://try.warden.cash/w/{address}` — the same scan, rendered for people. if a person hands you one of these links, call the scan api for the same address instead of reading the page. ## reading this site every page on warden.cash answers `Accept: text/markdown` with a markdown version (`Vary: Accept`), and has a static twin at `{path}.md` (`/index.md` for the home page). - [about](https://warden.cash/about): what warden is, who it's for, who builds it - [methodology](https://warden.cash/methodology): how a record is made - [privacy](https://warden.cash/privacy): what warden reads and keeps - [contact](https://warden.cash/contact): where to reach the contributors - [sitemap](https://warden.cash/sitemap.xml) ## what warden is not - not a voting tool. users are affected by governance, not participating in it. - not financial advice. every result is source-linked simulation.