Legal infrastructure · DOCX to structured data

Contracts, read verbatim by any agent.

Clauses, tracked changes, comments, definitions and cross-references, returned as structured data with per-view numbering.

Text, changes and comments are checked against the source on every call. The benchmark publishes the fixture results measured so far and identifies where real-document truth remains unreviewed. The parser is deterministic and makes no LLM calls.

This environment’s production configuration and retention monitoring are still under review. Do not submit confidential documents in this demonstration.

Read the API documentation

Live API demonstration

Inspect a Word document

Choose a .docx or .docm file. Nothing is sent until you select a file, accept the notice, complete verification if it is shown, and press Parse.

Checking whether the live demo is enabled…

The request is made to this site’s API. The product design processes plaintext in memory and does not write it to application logs or databases. Production settings and operations require owner review before these design statements are treated as a verified deployment claim. See the privacy draft.

For agents and applications

One contract, typed outputs, named views.

REST

curl --fail-with-body \
  -H 'Content-Type: application/octet-stream' \
  --data-binary @agreement.docx \
  https://verbatim.agmt.legal/v1/parse

JSON Schema and OpenAPI describe the response and error contracts.

Remote MCP

claude mcp add --transport http agmt-verbatim \
  https://verbatim.agmt.legal/mcp

Each tool’s annotations describe its actual quota and storage-metadata effects.