Noetis Legal · Business engine
Contract Review API for NDA and Vendor Agreements
Reviews an NDA or vendor agreement against your approved playbook.
Answers: "Can we check agreements against our own playbook inside our product?" For in house counsel and contract managers.
Not legal advice. Findings are for review by a qualified professional. This is about ordinary commercial contracts, not blockchain smart contracts.
Available today
ImplementedImplemented: runs on the shared runtime with supplied material. One bounded development check on 2026-10-12 took 135.6s with 16 model calls and ended "incomplete". That is a development signal, not an evaluation. Customer access is by approved account.
What you send
- Agreement text
- Approved playbook
- Jurisdiction (requested when material)
- Text material up to 150,000 characters per run
What comes back
- Clause linked issue table and proposed revisions for professional review.
- Findings with the located quote and a support status from claim review
- Release status: released, incomplete with reasons, or failed
- Executed roles, usage and measured cost
Sample
Authored illustration. Written by Encevra to show the workflow. Not customer data and not a recorded model output.
Review this NDA against our playbook.
PLAYBOOK: Term max 3 years. Mutual obligations only. Liability cap required. Governing law: New York. NDA (Acme and Brightline, v2): 1. Confidential Information means all information disclosed by Acme. 2. Recipient (Brightline) shall protect Confidential Information for 7 years. 3. Brightline shall indemnify Acme for any losses without limit. 4. This Agreement is governed by the laws of Delaware. 5. Section 6 governs return of materials. (No Section 6 is included.) 6a. Term: this Agreement ends after 2 years.
- Term of 7 years exceeds the 3 year playbook maximum (clause 2)
- One-way, uncapped indemnity conflicts with mutual obligations and the liability cap rule (clause 3)
- Governing law is Delaware, playbook requires New York (clause 4); clause 5 refers to a missing Section 6
The real response shape is documented in the API reference.
How the workflow operates
Each role is a responsibility in the workflow, served by a third party language model. More roles are not automatically better; depth and routing decide which run.
Built with
Models this engine uses: OpenAI (GPT), Anthropic (Claude), Kimi (Kimi (Moonshot AI)). Specialists run on OpenAI models and the claim review and final brief on Anthropic models. If a provider has a temporary failure, the step can fall back to an OpenAI model, and the run records that.
Contract Mapper
Identify parties, definitions, clauses and cross references.
Obligations Analyst
Extract responsibilities, deadlines, renewals and termination conditions.
Risk Allocation Analyst
Review liability, indemnity, warranties and remedies.
Playbook Reviewer
Compare terms against the customer's approved positions.
Consistency Reviewer
Detect conflicting clauses, missing definitions and version differences.
Revision Specialist
Propose clause edits tied to identified issues and the approved playbook.
Evidence and deployment
Evidence
This engine reads the text you send in the request. Each released finding carries the exact quote and its character span in that text, located mechanically before release. Quotes that cannot be located are labelled Insufficient evidence and never shown as source verified. Interpretation is reviewed as a separate step, and gaps such as a missing clause describe what was searched instead of citing text that is not there.
Deployment
Runs on Encevra hosted infrastructure using the third party models listed above. Every model call and fallback is checked against the deployment policy first. Private cloud and air-gapped deployment are planned; discuss deployment requirements.
What it does not handle
- Legal advice
- Broader legal research without validated source access
- Jurisdiction specific conclusions without a stated jurisdiction
- Uses only supplied material. No freshness guarantee beyond the documents provided.
- Required for every output during trials.
How to integrate
Send "engine": "legal" with your question and material from your server. Keys stay server side.
How to evaluate it
No published result for this workflow yet. Build a small answer key from your own work and compare against a strong single model baseline. See the evaluation checklist and method.
Cost and rights: pricing and licensing. Showing outputs to your own customers needs a written agreement.
Related engines
Content reviewed 2026-10-12 by the Encevra engine team. Engine version 0.1.0 on noetis-core-1.