Contract review, as an endpoint.
Post a document against one of your playbooks and get a run back. Subscribe to the webhook and the findings arrive the moment they exist, the same review, the same two scores and the same audit record as every other way into Vern.
Six calls is the whole of it.
Small enough to read in one sitting. Everything a review does in the app, it does here.
Multipart upload is supported everywhere a file_url is, if you'd rather not expose one. Both paths honour the same quota, the same scope and the same audit trail.
What goes out, what comes back.
Trimmed for the page, not invented, these are the shapes the reference documents.
Filter by band, by clause type, or by the playbook position they breach. Omit the filter and you get all eighteen.
Posting to the same deal is what makes it a round rather than a new contract, that's where the 0.5 rate and the diff come from.
Worth calling before a batch. If the period is nearly spent, submissions are refused rather than queued, so you'd rather know first.
If the run fails, it’s released and you’re charged nothing, a retry with the same idempotency key won’t double it either.
Never merged into one number: how far it sits from your position, and how well it’s drafted.
What improved, what regressed, and any clause that wasn’t in the version before.
The same figures as the usage screen, from the same table we invoice off.
You shouldn't have to poll us.
A review takes as long as it takes, usually under two minutes, longer for a hundred-page master agreement. So we push. Every event is signed, delivered at least once, and retried on a schedule you can plan around.
We retry at one minute, five, thirty, two hours and six, then dead-letter it. Nothing is silently dropped, failed deliveries are listed in the dashboard and you can replay any of them by hand.
Errors that tell you what to do next.
Every failure names the field, the limit or the reason. And the billing rule is the same one the rest of Vern runs on: if it didn't reach you, you didn't pay for it.
Send an Idempotency-Key with every submit and a repeat gets you the run you already have. Retries after a timeout, a redeploy or a queue replay cannot cost you a second credit.
The API isn't a separate meter. A first review is 1.0, a later round 0.5, re-running the same version is free, and a failure costs nothing, the same as an upload or a forwarded email.
How credits work →A key, a sandbox, then production.
Keys are issued per organisation and scoped to it, a key cannot see another customer's anything, and every call is attributed and audit-logged like any other action in Vern.
Versions are dated. Additive changes ship whenever they're ready; a breaking one gets a new date and twelve months' notice, and we tell you which of your keys is still on the old one.
Issued from your organisation’s admin area where API access is part of your agreement, with the rate limit set to whatever your volume needs.
Fixture contracts, deterministic scores, real webhooks. It consumes no credits, so hammer it.
Nothing else changes. Runs you create appear on the matter in Vern, next to the ones people made by hand.
Send us a contract from your own system.
Bring an endpoint and one real document to the call. We'll walk the whole exchange end to end, from the request to the signed webhook.