Ask whether a contract sent through Legalesign has been signed, and by whom.
Connect Legalesign with an API key and Memtro reads the documents each team has sent for signature, with status, each signer's progress and when they were signed, along with the team's templates. Signer emails, document text and signing links are never returned. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can send a PDF template to named signers, remind a signer, or reset a forwarded signing. Signers are usually outside the company and emails cannot be recalled. Voiding a document is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Legalesign tool, reads what it needs, and answers with the source cited.
These tools change something in Legalesign. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Legalesign for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Legalesign signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Legalesign is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Legalesign + MemtroHas the Northwind services agreement been signed yet?
Which documents in the Sales team are still waiting on a signer?
Who has opened the Brightwave Ltd NDA but not signed it?
Remind the second signer on the BigCo order form to sign it today
Send the mutual NDA template to Dan Fletcher at Globex for signature
Before the kick-off call the account lead asks whether the BigCo order form is signed. Memtro finds the document in the Sales team and lists its signers: Dan Fletcher signed on Monday, and the second signer has opened it but not signed.
Priya Nair asks Memtro to send the standard NDA to Tom Becker at Globex before Thursday's meeting. Memtro creates the document from the NDA PDF template and Legalesign emails Tom his signing link, with Priya copied to hear when he signs.
The teams that lean on Legalesign most, a question each of them asks, and what they connect beside it.
A record in Legalesign is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In developer.legalesign.com open API Keys, enter a key name, choose the REST interface (or both), create the key and copy it: it is shown once
New Legalesign accounts are sandbox-only, with 100 API calls an hour. Production needs a support ticket to Legalesign and a paid plan
In Memtro open Connections → Legalesign, paste the API key and connect
Ask which contracts sent this month are still waiting for a signature
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Legalesign tools are the same everywhere.
Only when you ask, and only what it has been granted: send a Legalesign PDF template to named signers for e-signature; send a Legalesign signer a reminder email; reset a forwarded Legalesign signing back to the earlier signer; void a Legalesign document (status removed, archived). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In developer.legalesign.com open API Keys, enter a key name, choose the REST interface (or both), create the key and copy it: it is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Legalesign for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
