ChatGPT and Claude NEW IN 2.0

Use Vern from the assistant you already have open.

Connect Vern to ChatGPT or Claude and ask it about a contract there. The assistant calls Vern rather than guessing, so the answer comes from your playbook and your document, with the same scoring and the same record as the dashboard.

ChatGPTExample Vern connector

What's our position on liability caps, and has Meridian met it?

Calling Vern · your scope
Read your playbook L-04 · cap ≤ 2× ✓
Clause 8.1 findings 12 Escalate · Weak ✓

Your position is L-04, capped at 2× annual fees. Meridian's 8.1 is uncapped, so it breaches that outright, and it scores Weak on enforceability too.

PLAYBOOK v11 · MERIDIAN ToB v2 NO CREDIT CONSUMED
Illustrative ChatGPT example · fictional contract
How
A remote connector
Tools
Four, scoped
Scope
Your org only
Record
Same as the app
Four things to ask · pick one

Your assistant. Your terms. Vern’s review.

Explore an example review, check your positions or ask what changed. Vern supplies the findings; your assistant brings them into the conversation.

Illustrative examples · fictional contract
ChatGPT Meridian Terms of Business Vern connected
New chat
Search chats
Projects
Today
Meridian Terms of Business
Q3 hiring forecast
Board pack wording
Yesterday
Osier renewal terms
Supplier onboarding
Candidate rejection note
What's our position on liability caps?
Used Vern
Read your playbook ✓
UK Client Terms · version 11 ✓

Position L-04 in your UK Client Terms playbook, version 11:

Aggregate liability capped at no more than 2× annual fees, with indirect and consequential losses excluded for both parties.

Your preferred position is 2× annual fees with mutual exclusions. Your fallback is 3× with agreed carve-outs. Anything outside those positions needs a decision from your legal adviser.

For this supplier-side review, uncapped liability is an escalation point in your playbook.

Read-only · playbook v11 · no credit consumed

Illustrative examples of Vern in ChatGPT and Claude, using fictional contract data. Screens and responses may vary. Vern is an independent integration, not endorsed by OpenAI or Anthropic.

The four tools

A narrow set, on purpose.

The connector exposes four things and nothing else. It cannot browse your matters at will, export in bulk, or change a playbook, because an assistant with a broad grant over your contracts is a worse idea than it first sounds.

analyze_contract
Run a review

Submits a document and returns the run. Consumes a credit exactly as any other intake path does, and respects your quota.

get_findings
Read the results

Both scores, impact and suggested wording per clause, for a run you already have. Never a free-text summary.

ask_vern
Ask about a contract

The same tool-using chat as the app, so the answer your assistant gives is the answer Vern would have given.

list_playbooks
Read your positions

Read-only. Your positions and their fallback tiers, from the published version. Editing stays in the app.

Connecting it

Three steps, and an admin decides who gets it.

The connector is enabled per organisation, and each person authorises it as themselves. What they can reach through the assistant is exactly what they can reach in the app, no more, and never another organisation's anything.

Tokens are listed and revocable in settings, and every call is attributed to the person who made it.

01
Add the connector

In ChatGPT or Claude, add Vern from the directory or by URL.

02
Sign in as yourself

You authorise it with your own Vern account, so your role and scope carry across.

03
Ask it something

Nothing else to configure. Reviews you run there appear on the matter in Vern.

Feature-gated per organisation · revocable per person
What this isn’t

Your contracts, handed to a chatbot

The assistant never receives your contract to read. It calls a tool, Vern does the work under your organisation's scope, and a result comes back. The document text stays where it was.

Which is the difference between using an assistant as an interface and using it as the analyst.

Same rules as everything else

Scoped, logged, revocable

Row-level security applies to every call
Quota and feature gates enforced server-side
Every call attributed and audit-logged
Revoke a person’s access without touching anyone else’s

Your assistant provider's own data handling is between you and them, worth checking before you enable it.

Ask your own assistant about your own contract.

We'll connect it on the call and you can put a real question to it in whichever one your team already lives in.