Condicio is a JSON Schema 2020-12 standard for what AI extracts from contracts — parties, obligations, risks, financial terms, and more. Open, confidence-aware, and built for interoperability.
Every CLM platform and AI extraction tool defines its own output format. Condicio gives them a common language.
Designed for the output of AI contract extraction, not for drafting or execution. Every field can carry a confidence score.
Every extracted value can be traced to its source with field-level confidence scores — essential for AI-generated data.
Types are reusable $defs with cross-references. Adopt just the sections you need — a valid document can use as few as three fields.
Apache 2.0 licensed with a community RFC process. No single vendor controls the standard or the data it describes.
ISO 8601 dates, ISO 4217 currencies, BCP 47 languages, JSON Schema 2020-12. Reduces the learning curve for adopters.
Use Condicio as an interchange format between CLM platforms, extraction engines, and analytics tools. No more custom field mapping.
Nine top-level sections, composable via $defs, validated by a single JSON Schema 2020-12 document.
Condicio serves as the interchange layer for the entire contract intelligence ecosystem.
Any extraction engine can produce Condicio as its canonical output format, decoupling extraction from downstream applications.
Migrate between platforms without custom field mapping. Export from one CLM in Condicio, import into another.
Extract obligations with deadlines, status, and cross-references to source clauses. Feed into task management systems.
Aggregate contract data across entities and jurisdictions into a unified corpus for cross-portfolio risk and financial analysis.
Extract compliance-relevant clauses (GDPR, SOX, HIPAA) into structured data for automated reporting and gap analysis.
Standardized contract data extraction across thousands of target-company contracts during acquisition due diligence.
Validate your first Condicio document in seconds.
npx ajv validate -s schema.json -d document.json
Install the schema package and validate with AJV.
npm install condicio-schema
pip install condicio
Validate and work with Condicio documents as typed Python objects.
condicio validate document.json
Paste a Condicio document into the live validator to check it against the schema in real time — no install needed.
Clone the repo and run the test suite with existing examples for NDA, service, employment, and license agreements.
git clone https://github.com/docfide/condicio cd condicio && npm install && npm test
Validated Condicio documents across four common contract types, in JSON and YAML.
| Contract Type | Highlights | Files |
|---|---|---|
| NDA | Mutual confidentiality, exclusions, survival period, auto-renewal | JSON · YAML |
| Service Agreement | $150K milestone payments, IP assignment, liability cap | JSON · YAML |
| Employment Agreement | $350K salary + bonus + equity, non-compete, severance | JSON · YAML |
| License Agreement | $250K license + $50K maintenance, SLA, audit rights | JSON · YAML |
Profile-specific examples:
| Contract Type | Profile | Files |
|---|---|---|
| ISDA Master Agreement | Financial Services | JSON |
| Clinical Trial Agreement | Life Sciences | JSON |
| Lease Agreement | Real Estate | JSON |
| SaaS Agreement | Technology | JSON |
Extend the base schema with domain-specific fields for common contract types. Profiles inherit all base fields and add their own via allOf + unevaluatedProperties.
ISDA Master Agreements, credit facilities, subscription agreements — with tranches, covenants, credit support, events of default, derivative transactions, capital commitments, and distribution waterfalls.
Clinical trial agreements, research collaborations, licensing — with clinical study data, regulatory obligations, enrollment targets, publication rights, data rights, milestone payments, royalties, fields of use, and patent prosecution.
Commercial leases, subleases, and property management agreements — with premises details, lease term, rent schedules, abatements, security deposits, operating expenses (CAM, taxes, insurance), tenant improvements, use clauses, assignment/subletting, repair obligations, insurance requirements, options (renewal, expansion, ROFR), and estoppel certificates.
SaaS, software license, cloud service, and support agreements — with license metrics, service level agreements, support tiers, maintenance windows, usage limits, data processing provisions, professional services scope, and restrictive practices (audit rights, non-solicit, MFN pricing).
Profiles are just JSON Schema 2020-12 documents that reference the base via $ref. Anyone can create a profile for their vertical — energy, government contracts, or internal CLM-specific fields.
How Condicio fits in the legal data standards landscape.
| Standard | Focus | AI Extraction | Confidence | Open Standard | JSON Schema |
|---|---|---|---|---|---|
| Condicio | Contract extraction output | ✓ | ✓ | ✓ | ✓ |
| Accord Project | Contract drafting | — | — | ✓ | ✓ |
| SALI | Contract metadata tagging | — | — | ✓ | — |
| LEDES | Legal billing / invoices | — | — | ✓ | — |
| LegalXML | Court filings | — | — | ✓ | — |
| OCDS | Public procurement | — | — | ✓ | ✓ |
Open evolution through a community RFC process.
Anyone opens a GitHub issue using the RFC template with motivation, schema diff, example document, and backward compatibility analysis.
Minimum 7-day open comment period. Community feedback on scope, naming, and alignment with existing conventions.
Maintainer validates schema correctness, example conformance, and documentation. Accept, reject, or defer to a future major version.
Semantic versioning: MAJOR for breaking changes, MINOR for additive changes, PATCH for fixes. Backward compatibility guaranteed within minor versions.
Condicio is an open project built by Docfide. Contributions welcome.