Works in CodexComing soon

Contracts.io in Codex

Register Contracts.io with Codex and draft from the terminal: an SOW for the project you are scoping, an NDA before the kickoff call. Codex prints the room link; you take it from there.

~/clients/northwind · codex
› Draft an SOW for Northwind: website rebuild, £18,000, three milestones, six weeks.
• Calling contracts.create_draft (asks first)
Allow Contracts.io to create a draft? [y/N] y
✓ Lex drafted “Statement of work · Northwind website rebuild”
1 Scope · 2 Milestones (3) · 3 Fees £18,000 · 4 Acceptance · 5 Liability
Status: draft · not sent · only you can see it
Room https://contracts.io/d/northwind-sow
Review & send in Contracts.io. Signing happens there, with you.
›

What you can do

Reads freely. Asks first. Never signs.

Every tool Codex can call falls into one of three tiers. The riskier the action, the closer it stays to you.

01

Runs automatically

Read-only. Nothing changes.

  • list_contractsEvery contract you are part of, with status.
  • get_contractOne contract, clause by clause.
  • whats_waiting_on_meProposals and replies that need you.
  • explain_clauseAny clause in Plain English.
02

Asks you first

Your AI asks before each one. Nothing is sent.

  • create_draftLex drafts a new contract from a sentence.
  • propose_changeStage a redline or a counter.
  • respond_to_proposalStage an accept, counter or decline.
03

Only in Contracts.io

No tool exists for these. You do them in the app.

  • SendSharing a draft or a reply with the other side.
  • InviteAdding people to the contract room.
  • Request signaturesFreezing the final version for signing.
There is no sign tool.Signing always happens with you, in Contracts.io.

Set up Codex

Connected in a minute.

Three steps in the Codex CLI. You sign in once; Codex only sees the contracts you are part of.

Run in your terminalComing soon
Terminalcodex mcp add contracts --url https://mcp.contracts.io

Not live yet. The address is reserved and opens when the connector launches.

  1. 01

    Register the server

    Run the command above in your terminal. Codex saves Contracts.io to its config for every session.

  2. 02

    Sign in once

    The first call opens a browser to sign in to Contracts.io. Approve it and come back to the terminal.

  3. 03

    Ask for a draft

    Describe the deal. Codex asks before creating a draft, then prints the room link to review and send.

Use cases

Four things people ask first.

Say it the way you would to a colleague. Codex picks the right tool.

Draft from a sentence

“NDA with Kestrel before Thursday’s call, mutual, two years.” Lex drafts it and hands back a link.

Draft a mutual NDA with Kestrel, two years

Check what’s waiting

One question across every contract: who proposed what, on which clause, and how long ago.

What’s waiting on me?

Counter a clause

Say the number you want. Lex stages the counter with a short note; you send it when you are happy.

Counter Clause 5 at 9 months

Explain a clause in Plain English

Paste or name any clause. Get what it means for you, without the legal wording getting in the way.

What does the indemnity clause mean for me?

FAQ

Questions, answered.

Data, the other side, and what your AI can and cannot do.

TBD: we don’t train on your contracts. (Placeholder until the data policy is confirmed and published.)

No. They open the same Contracts.io link in a browser, with no account and no AI tool needed. Codex is just one way for you to work.

No. Sending, inviting and requesting signatures only happen in Contracts.io. There is no sign tool: signing always happens with you.

Nothing. Reading and explaining run on their own. Drafting, proposing a change and responding to a proposal ask you first, and even then nothing is sent.

Not yet. The connector is coming soon. Draft in Contracts.io today and your contracts will be there when it opens.

What are you agreeing?

Describe it in a sentence. Lex drafts the first version.