Contract Operations API

Extract numbered clauses, parties, defined terms, and a governing-law sentence from supplied contract text or a text-based PDF. Each item keeps a source excerpt. Missing headings stay unavailable.

Extract sentences that use shall, must, agrees to, is required to, or undertakes to, and name the party stated before the verb. Sentences that only say may are not turned into obligations.

Extract stated periods, notice periods, and unambiguous calendar dates. Slash dates are not guessed, and a deadline is not created when the text gives no number or date.

Read renewal and expiration wording that is actually printed. A notice date is calculated only from a stated expiration date and a stated notice period. Renewal wording is flagged as a potential risk, not a legal conclusion.

Compare the contract with a checklist or with provisions supplied for a named standard. A standard name alone does not create required clauses, and similar wording is not inferred.

Compare two supplied contract versions by clause number or heading. Whitespace and letter case alone are not reported. Clauses are not matched by meaning.

Label meaningful version changes as a date, a stated period, an obligation verb, or an added or removed clause. The legal effect of a change is not decided.

Group extracted obligations under the party named before shall, must, or agrees to. An obligation that names no party stays unassigned.

Flag renewal, indemnity, unlimited-liability, and termination-for-convenience wording that is present in the text. These are potential risks, not a legal opinion or a risk score.

Combine clause, obligation, deadline, renewal, checklist, party, and risk checks. checklist_satisfied means the supplied phrases were found. It is not a legal compliance determination.