ZICO

Contract AI layer

Zico AI Contract-native capabilities

Review, quick review, compare, translate, extract, summarize, minutes. Plug into a CLM or OA you already run, or deploy with Zico Contract System.

Two ways to use it

API or iframe

If you already have a CLM or OA, keep the ledger. The server calls the open API; the handler’s page embeds an white-label iframe.

Pack with Zico Contract System

If you need draft, approve, sign, and fulfill, deploy with the contract system. Workflow stays there; contract intelligence stays in Zico AI.

Seven work surfaces

All callable over the API. Review, compare, and translation can also sit inside pages you already have. Any result can be questioned further, with answers cited to the source text.

  • Contract review

    Stance-aware, back on the page

    Scan parties, payment, default, venue, and IP by buyer/seller stance. Present findings and missing clauses are separate. Legal-basis checks run after the risk list is complete.

    • Risks anchored to source; opinions exportable (verbatim patches optional)
    • Internal checklists are configurable
    • With attachments, the contract package is reviewed together: the main contract is checked item by item against task statements, budgets, and amendments
    • Negotiation audio can be attached as contrast; talk does not replace the text
    • Amounts in figures vs. words and dates are checked by code, which also catches scan-recognition errors

  • Quick review

    In-house Zev model, pros and cons in seconds

    Zev, a model built in-house by Zico AI, answers a fixed checklist clause by clause and extracts what each clause says, such as whether payment depends on an invoice or how far breach consequences are spelled out, and marks which party each term favors. A contract of one or two hundred clauses returns in seconds. When you need clause-by-clause opinions and fixes, send it on to contract review.

    • Choose Party A or B; each term is marked for or against you, with both sides' breach consequences compared
    • Lists terms the contract may be missing; answers the model is unsure of are marked for checking
    • Runs on your GPUs if you have them, otherwise on FIM compute; never on third-party model services
    • 1 credit per contract, any length. Chinese contracts only for now

  • Version compare

    Material changes apart

    Clause-level diff of two contracts. Material and non-material changes are separate. Word and text-layer PDF can be read against each other. Both versions can also run through quick review to flag the edits that change a checklist answer.

    • Edits map back to source
    • Edits that change checklist answers are flagged
    • Each edit can be rated for risk, with a suggested response, from your side of the deal
    • Commercial-term changes can be summarized
    • Comparison reports export

  • Translation

    Numbers that match

    Translation follows clause structure, with a glossary locking terms. Numbers, dates, and amounts that drift from the source are flagged. Missing segments are counted, not invented.

    • Source and target side by side
    • Client glossary
    • Target and bilingual export

  • Extraction

    Back into your ledger

    Parties, subject, amounts, terms, and payment nodes become structured results. The ledger and reminders stay in the contract system or the system you already run.

    • Configurable field schema
    • Missing required fields listed
    • Return over the API

  • Summary

    One page for this contract

    Main-contract points plus attachment contrast. If negotiation audio is attached, the transcript is read in and mismatches are marked.

    • A short brief, not a chat reply
    • Zero mismatches still state how many attachments were read
    • The whole brief exports

  • Meeting minutes

    Audio you can replay

    After transcription, minutes are written to a chosen focus. Speakers can be named by a person; timestamps play back.

    • Minutes, transcript, and digest are separate artifacts
    • Names are human-assigned; there is no voice ID
    • Word / PDF / Markdown export

COMING SOON

From findings to a revision-ready file

After a person confirms proposed changes in the workbench, Zico AI will create a new file with comments or tracked revisions without overwriting the original. The contract system or downstream application then retrieves it and owns the business version and workflow.

  1. Human confirms
  2. Create redline
  3. Append new file
  4. Downstream retrieves

Built into how you already work, not another app to open

Into systems you already run

Open API for the server, white-label iframe for the handler’s page. Ledger, approval, and permissions stay with you.

Outputs you can check

Risks, diffs, and translations anchor to source text. People confirm before a process takes over. Opinions export; verbatim patches can be omitted.

Private-ready

System and data can live in your environment. Contract text stays in the instance.

Zico AI service whitepaper

Capability limits, the full credit rules, data flow, and private-deployment requirements in one document. Leave your email and we will send you a reading link.

Request the whitepaper

Walk one full path against the system you already have

If you have a CLM or OA, we show API and iframe. If you need the full lifecycle, we show the pack with the contract system.

Book a DemoSee the contract system
Contract reviewQuick reviewVersion compare