post_v1_legal_filings
CreateLegalFiling records a filing of one or more of the org's documents with a state or agency, and returns the tracking record. It is a TRACKING record, not an autonomous filing.
CreateLegalFiling records a filing of one or more of the org's documents with a state or agency, and returns the tracking record.
It is a TRACKING record, not an autonomous filing. With no filing partner wired the honest status is "manual" and the note says so: the documents were generated for signature, and the org files them through its registered agent. Nothing here invents a filing id it does not have.
Every document id must belong to the caller's org; one that does not is a 404 naming it, so a filing can never reach across tenants.
| Tool | post_v1_legal_filings |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | POST /v1/legal/filings |
| Product | legal |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
documentIds | string[] | — | — | — | DocumentIDs are the documents to file. At least one is required, and every one must belong to the caller's org — a filing can never reach across orgs. |
jurisdiction | string | — | — | — | Jurisdiction is the state or agency the filing is for, e.g. "DE". |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_legal_filings",
"arguments": {
"documentIds": [
"<documentIds>"
],
"jurisdiction": "<jurisdiction>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_legal_filings | POST /v1/legal/filings | legal | Records a filing of one or more of the org's documents with a state or agency, and… |
The same capability over plain HTTP is in the legal API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
post_v1_legal_documents_id_sign
RequestLegalSignature opens an e-signature request over one document and moves it to out_for_signature, returning the provider's reference for the request.
put_v1_legal_templates_id
SaveLegalTemplateOverride saves the org's own version of a template — a custom NDA, a house MSA — and returns it with its new version number.