> ## Documentation Index
> Fetch the complete documentation index at: https://docs.natural.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When building application code, use `@naturalpay/sdk` for TypeScript or `naturalpay` for Python.
> When operating Natural directly for a user, use the payments MCP at `https://mcp.natural.com`.
> When searching Natural documentation, use the docs MCP at `https://docs.natural.com/mcp`.
> Use the Natural CLI for terminal and CI automation.
> Use REST only for unsupported languages or when the user explicitly requests raw HTTP.
> Start integration development and testing in the sandbox. Do not use production unless the user explicitly requests it.
> For sandbox requests that require `customerPartyId`, list customers first. Reuse only the intended fixture; otherwise create a customer.
> REST and SDK amounts use integer minor units. Payments MCP amounts use decimal strings with a required currency code.

# Overview

> Third parties with whom you transact over Direct

<Note>Direct is in early access. To request Direct access, contact [hi@natural.com](mailto:hi@natural.com).</Note>

An external party (`epty_*`) is an individual or business not on Natural, with whom you can transact over Direct rails like ACH. Banking details attach to them as [External party accounts](/guides/concepts/external-party-accounts).

Create an external party with its kind — individual or business — and a name. Email, phone, and a mailing address are optional; Natural normalizes phone numbers to E.164.

```json theme={null}
{
  "data": {
    "attributes": {
      "kind": "individual",
      "name": "Jordan Rivera",
      "email": "jordan@example.com"
    }
  }
}
```

The response returns the new party's ID. Reference it when you [store banking details](/guides/concepts/external-party-accounts), then move money to those accounts with an [ACH payment](/guides/concepts/ach).
