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

# Public alpha endpoints

> Client-facing Directory, Relay, and Cache URLs for the OpenPayload public alpha

These production-hosted OpenPayload services are available for **public alpha testing**. OpenDispatch remains alpha software and is not suitable for sensitive or production communications.

| Service | Public alpha base URL | Intended use |
| - | - | - |
| [Directory](/openpayload-directory-api) | `https://directory-1.use2.openpayload.io:443` | Resolve decentralized identifiers, public keys, service endpoints, and delivery policies; submit authorized public-state changes. |
| [Relay](/openpayload-relay-api) | `https://relay-1.use2.openpayload.io:443` | Submit application-encrypted DDN envelopes for live delivery toward recipients. |
| [Cache](/openpayload-cache-api) | `https://cache-1.use2.openpayload.io:443` | Temporarily retain encrypted envelopes under recipient policy, then let authorized recipients retrieve and acknowledge them. |

These are **base URLs**. Add the route documented in the corresponding API reference. For example, use `GET /resolve/{did}` with a Directory or `POST /relay` with a Relay.

For delivery to a particular recipient, resolve their identifier and follow its published service endpoints and applicable delivery policy. A recipient may use different Relay or Cache operators. Encrypt the payload in your client before submitting it; never send a private key or seed phrase to a node.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.