[ Docs ](https://sendnda.com/docs)     

 [ Agents and the API ](https://sendnda.com/docs/agents)     

The four tools
==============

create-nda, list-ndas, get-nda and resend-nda, and what each one answers.

 05

Agents and the API
------------------

Article 2 of 3

 Connected over MCP, your assistant gets four tools. They all act on your account, and they all see the same NDAs: the ones created on your account, plus the ones sent from your verified email address through the public site. An NDA is named by its `uuid`, which `list-ndas` and `create-nda` return.

create-nda
----------

Creates an NDA and emails the signing links to you and the recipient **at once**. There's no draft step, so your assistant should confirm the details with you first.

Only two fields are required: `recipient_name` and `recipient_email`. The recipient fills in their own address when they sign. Everything else has a default:

 | Field | Default |
|---|---|
| Your name, email, company and address | Taken from the last NDA on your account; your name and email fall back to your profile |
| `disclosing_party` | `sender`; or `recipient`, or `both` for mutual |
| `ai_use` | `business`; or `strict`, or `open` |
| `duration` | 3 years, from 1 to 5 |
| `confidentiality_duration` | 3 years after it ends, from 1 to 5 |
| `purpose` | Evaluating, and if the parties decide so, pursuing a business relationship |
| `has_non_solicitation`, `has_non_circumvent`, `has_penalty`, `includes_affiliates` | All off. `has_penalty` only takes effect when your address is in the Netherlands. |

Your first NDA has nothing to default from, so it needs your street address, city, postal code and country, the last as a lowercase two-letter code like `nl` or `us`. For the United States, Canada, Australia and the United Kingdom it also needs `sender_address_state`, because that fixes the governing law. See [Governing law](https://sendnda.com/docs/the-agreement/governing-law).

The answer is the NDA's summary plus `sender_url`, your own signing link.

list-ndas
---------

Lists your NDAs, newest first. Each entry is a summary:

```
{
  "uuid": "…",
  "status": "viewed",
  "recipient_name": "Sam Okafor",
  "recipient_email": "sam@lumen.co",
  "created_at": "2026-09-21T10:42:00+00:00",
  "sent_at": "2026-09-21T10:42:00+00:00"
}
```

It takes two optional fields. `status` filters on one of `sent`, `viewed`, `awaiting_sender` or `completed`. `limit` caps the list between 1 and 100, and is 25 when left out.

get-nda
-------

Takes a `uuid` and returns the whole NDA: the summary, both parties with their name, email, company and address, the terms, the audit trail and `sender_url`.

- **terms**: who discloses, the AI tools level, the purpose as the contract states it, the governing law, every clause that takes effect (non-disclosure, and any of non-solicitation, non-circumvent, penalty for a breach and group companies), and both durations in years.
- **audit\_trail**: when and from which IP address the recipient viewed and signed, and when and from which IP address you signed. A step that hasn't happened is left out.

resend-nda
----------

Takes a `uuid` and emails the recipient their signing link again. It only works while the NDA has been sent and the recipient hasn't signed. It answers with the address it sent to.

Statuses and errors
-------------------

An NDA moves through `sent` (the emails went out), `viewed` (the recipient opened it), `awaiting_sender` (the recipient signed, and you countersign through your `sender_url`) and `completed` (both signed, and both of you get the sealed PDF by email). An NDA from the public site whose sender hasn't confirmed their email address yet doesn't belong to your account, so no tool returns it.

Treat `sender_url` as private. Anyone with it can act as you on that NDA. A `uuid` that isn't on your account answers with an error that won't change, so your assistant shouldn't retry it.

 Checked against the code on 21 September 2026.

 [   Connect over MCP ](https://sendnda.com/docs/agents/connect-over-mcp) [ API tokens   ](https://sendnda.com/docs/agents/api-tokens)