# LitigationWatch

> LitigationWatch watches Australian companies for litigation. Every day it checks courts and tribunals across every Australian jurisdiction for the companies on a watchlist and emails the account owner when one is named in a case. AI agents can run the whole service for an owner over plain HTTPS and JSON on this site: no SDK or MCP server.

The owner approves an agent's access and pays; the agent manages the watchlist, reads alerts and sets up alert rules (signed webhooks). Plans: Standard US$9/month for 20 companies, Pro US$29/month for 100.

## Quick start for agents

1. Get access (OAuth 2.0 device flow, RFC 8628, no registration): `POST https://litigationwatch.dev/oauth/device_authorization` with form fields `client_id` (a short name for you), `client_name`, and `login_hint` (the owner's email: we email them an approval link). Show the owner `verification_uri_complete` if no email was sent.
2. Poll `POST https://litigationwatch.dev/oauth/token` with `grant_type=urn:ietf:params:oauth:grant-type:device_code`, `device_code` and `client_id` every `interval` seconds until you get `access_token` (1 hour) and `refresh_token` (single use; refresh with `grant_type=refresh_token`).
3. Call the API with `Authorization: Bearer <access_token>`. Start with `GET https://litigationwatch.dev/api/v1/account`: it returns the plan, usage and `next_steps`.
4. No active plan? `POST https://litigationwatch.dev/api/v1/billing/checkout` with JSON `{"plan":"standard"}` (or `"pro"`, and `"email_owner": true` to email it) returns `checkout_url`. Give it to the owner; they pay on Stripe. Agents never pay.
5. Find exact legal names: `GET https://litigationwatch.dev/api/v1/directory?q=<name or ACN>` (no token; 15,340 companies). Add companies: `POST https://litigationwatch.dev/api/v1/companies` with `{"companies":[{"acn":"..."},{"legal_name":"..."}]}`.
6. Alerts: poll `GET https://litigationwatch.dev/api/v1/alerts?since=<highest id seen>`, or `POST https://litigationwatch.dev/api/v1/alert-rules` with `{"name","url","filter","schedule"}` to have matching alerts POSTed to your HTTPS endpoint (HMAC-signed). The owner still gets alert emails.

Errors are RFC 9457 problem+json with a `hint` saying what to do next. Only GET and POST are used.

## Docs

- [Agent guide](https://litigationwatch.dev/agents.md): full walkthrough with examples, scopes, alert rules, webhook signatures, errors and limits
- [OpenAPI 3.1 schema](https://litigationwatch.dev/openapi.json): every endpoint and object
- [OAuth authorization server metadata](https://litigationwatch.dev/.well-known/oauth-authorization-server)
- [OAuth protected resource metadata](https://litigationwatch.dev/.well-known/oauth-protected-resource)
- [API catalog](https://litigationwatch.dev/.well-known/api-catalog)

## Site

- [Home](https://litigationwatch.dev/index.md): what LitigationWatch does
- [Pricing](https://litigationwatch.dev/pricing.md): plans and limits
- [Security](https://litigationwatch.dev/security.md): how data is protected
- [Company directory](https://litigationwatch.dev/au/company/index.md): 15,340 Australian company pages; each is also Markdown (add index.md)
- [Terms](https://litigationwatch.dev/terms.md) and [Privacy](https://litigationwatch.dev/privacy.md)

## Optional

- [Full guide as one file](https://litigationwatch.dev/llms-full.txt)
- Every HTML page is also served as Markdown: add `.md` to the path or send `Accept: text/markdown`.