Solutions
Contracts for enterprise teams.
A large company holds more contracts than any one person has read. contracts.io is built so the contracts you already have and the ones you make next stand in one place, in words a person can check, with your systems wired to the same verbs a person presses.
For enterprise
What a large company can do here.
Bring the contracts you already hold
Import takes Word, PDF, plain text and Markdown. Each import makes two objects: the original file, kept as it was, and a contract made of its words. The blocks the parse was least sure of are listed, each pointing back at the original, so a person checks the uncertain lines first.
How imports workAsk a question across everything you can open
Ask in English. The answer arrives as its citations: the contract, the block, the exact span and the quoted words. Retrieval runs on the asker's own access, so a contract you cannot open cannot be cited, and cannot be counted.
Ask, in the API docsWire it into the systems you already run
The API has the same verbs as the app: draft a contract from a sentence or a template, import a document, stage a decision. Webhooks tell your systems when a letter lands, when the words change and when a signature binds. There is no envelope and no routing order. The API is written down in full before it is built, and the docs say so on every page.
The API, from the startAn agent holds one person's seat
A connected agent acts as the person who connected it, within the ceiling the organisation sets, and can never send or sign. Send-class calls stop and hand back the assembled sheet for a person to press. No key, scope, flag or setting removes this.
MCP, in the docsGoverning law for every entity
A contract names a legal unit, not a country, and may name more than one: one law for the agreement, another for the forum, a schedule with its own. 184 legal systems are in the picker, and a country that holds several is a heading rather than a choice.
Every governing lawStart with a template
Kinds from the catalogue that fit this desk.
- Services agreementIn the libraryThe contract behind ongoing work for a client: what you will do, what it costs, who owns the result, and how either side ends it.
- Data handling agreement, globalIn the libraryThe same job as the US data contract, written for work that crosses borders — the version a European customer usually asks for.
- Data sharing agreementTwo organisations exchange data as equals rather than as customer and supplier: what is shared, why, and what each may do with it.
- Service level agreementThe measurable promises attached to a service: availability, response times, how they are measured, and what happens when they are missed.
- Supply agreementA standing arrangement to keep supplying: volumes, lead times, prices over time, quality, and what happens when supply fails.
- Two-way confidentiality agreementIn the libraryBoth sides expect to hear things they should not repeat, so both sides promise.
Governing law this desk often names: England and Wales, New York, Singapore, Ireland — or several at once. Every governing law.
Start with the next contract, not the whole archive.
The other side never pays and never makes an account.
Last reviewed by the contracts.io editors. How these pages are written.