Integration

Proof integration

Proof (formerly Notarize) runs online notarization, eSign and identity verification. Create transactions (as drafts or sent at once), add documents, send drafts to signers, cancel, recall, re-send invitations, track status, download audit trails, manage in-house notaries, read notarization meeting records, cost centers and templates, and manage V2 webhooks. Sent transactions are billed per transaction at the plan's rates (business list prices: $25 per Notarize Network meeting, $4 per Sign transaction, $4 per identity verification). Withheld on purpose: signer contact and identity data (e-mail, phone, address, birth date, ID images), access links, document and recording URLs and webhook URLs, headers and keys; left out: transaction updates, webhook updates, the v1 webhooks, test-only force complete, integrations, OpenID Connect, partner and referral routes. API access needs a plan that includes it (Pro+ or above for businesses). Authentication: a Full Access API key (prf_...) from Settings, API Keys, sent in the ApiKey header.

Connect Proof How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Proof.Built from the 31 Proof tools below, on the connection you add once.

What you can do with Proof

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transaction, 9 operations

activate_transactionActivate transactionPOSTSends a draft transaction to its signers for real (e-mail unless suppress_email) and starts the billed workflow. Call it once every document's processing_state is done. Returns the transaction.
cancel_transactionCancel transactionPOSTCancels a transaction for real, so signers can no longer complete it. Returns the transaction.
create_transactionCreate transactionPOSTCreates a notarization, eSign or identity transaction. draft=false sends it to the signers by e-mail (and SMS) at once and starts billing; draft=true keeps it editable until activate_transaction. Returns it.
delete_transactionDelete transactionDELETEDeletes a transaction for good. Returns a confirmation message.
get_transactionGet transactionGETReturns one transaction: status and detailed_status, dates, cost, documents (ids, names, requirement, processing state) and per-signer ids and signing status.
list_transactionsList transactionsGETLists transactions, newest first, 10 per page by default (limit up to 1000, offset to page), filterable by status and created or updated date. Signer identity and contact data are withheld.
recall_transactionRecall transactionPOSTRecalls a real estate transaction already sent back to draft so it can be changed; the signer is e-mailed that the closing documents are being updated. Returns the transaction.
resend_transaction_emailResend transaction emailPOSTRe-sends the transaction invitation e-mail to the signers for real. Returns the transaction.
resend_transaction_smsResend transaction smsPOSTRe-sends the transaction access link to the signers by SMS for real, to the phone numbers given on the transaction's signers. Returns the transaction.

Notary, 5 operations

create_notaryCreate notaryPOSTCreates an in-house notary account in your organization for real; Proof's compliance team reviews it (status needs_review until compliant). Returns the notary.
delete_notaryDelete notaryDELETEDeletes an in-house notary from your organization for good.
get_notaryGet notaryGETReturns one in-house notary: names, commission state and compliance status.
list_eligible_notariesList eligible notariesGETLists the notaries of your organization eligible to take a transaction's meeting (names, state, compliance status).
list_notariesList notariesGETLists your organization's in-house notaries (names, commission state, compliance status), optionally for one state or child organization.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a webhook for real: Proof POSTs each subscribed event to the URL. Sign deliveries with signing_key (else the API key signs them). Returns its id and events.
delete_webhookDelete webhookDELETEDeletes a webhook for good; Proof stops sending it events.
get_webhookGet webhookGETReturns one webhook: enabled flag, subscribed events and request id header name.
list_webhooksList webhooksGETLists your webhooks: id, enabled flag and subscribed events (receiving URLs, headers and keys are withheld).
send_test_webhookSend test webhookPOSTSends a test event to your webhook endpoints for real, to check your receiver. Returns the event sent.

Document, 4 operations

add_documentAdd documentPOSTAdds a document to a draft transaction from a PDF URL, base64 PDF or template permalink (at most 50 MB). Returns the document; wait for processing_state done before activate_transaction.
delete_documentDelete documentDELETERemoves a document from a draft transaction for good. Returns a confirmation message.
get_documentGet documentGETReturns one document of a transaction: name, requirement, processing and completion state; with encoding=base64 also the file content as base64 in data.
update_documentUpdate documentPATCHChanges the fields sent of a document of a draft transaction (name, requirement, witness, annotations, tracking id). Returns the document.

Notarization record, 2 operations

get_notarization_recordGet notarization recordGETReturns one notarization meeting record: meeting start and end, notary name and how the notary was sourced.
list_notarization_recordsList notarization recordsGETLists notarization meeting records (meeting start and end, notary name and source), 20 by default. Signer identity data, IDs, recordings and document links are withheld.

Audit trail, 1 operation

get_audit_trailGet audit trailGETReturns the audit trail PDF of a transaction (who did what and when) as a file.

Cost center, 1 operation

list_cost_centersList cost centersGETLists your organization's cost centers by name (10 per page by default, up to 1000); pass an id as cost_center_id on create_transaction.

Organization, 1 operation

get_organizationGet organizationGETReturns the id and name of the organization the API key belongs to.

Template, 1 operation

list_templatesList templatesGETLists your document templates (100 per page by default, up to 1000); pass an id as template_id on add_document.

Webhook event, 1 operation

list_webhook_eventsList webhook eventsGETLists the events sent to a webhook with when each was delivered and the HTTP status your receiver answered (payloads withheld), 20 by default, up to 100.

Webhook subscription, 1 operation

list_webhook_subscriptionsList webhook subscriptionsGETLists the event names a webhook can subscribe to, for transactions and for notaries.

Use Proof from Claude Code, Cursor or Codex

Connect Proof in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Proof operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Proof

Create your workspace
Sign up free. Nothing to install.
Connect Proof once
Add your Proof connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.