Skip to main content
Monk needs a personal access token to provision and manage infrastructure in your DigitalOcean account. This is the simplest credential setup of all four cloud providers.

What you need

  • Personal Access Token (API token)
  • Optional: default region (e.g., nyc1)

Create credentials

1

Open the API page

2

Generate a token

Click Generate New Token. Name it something like monk-deployment. Check both Read and Write scopes.
3

Copy the token

Copy the token immediately. It is shown only once.
4

Provide to Monk

When you deploy to DigitalOcean, Monk requests the token through a secure local form, never through the chat. You can also tell your agent:

Required permissions

The token needs both Read and Write scopes. DigitalOcean tokens are all-or-nothing: there is no fine-grained permission model like AWS IAM.

How credentials are stored

You enter credentials in a form in the local dashboard, never in chat. Monk keeps them in your OS keychain (or an encrypted file where there is no keychain) on your computer and pushes them to your cluster when a deployment needs them. The coding agent never sees the values. See Security.

Troubleshooting

Token revoked: generate a new token on the API page and update credentials in Monk. Insufficient scopes: make sure the token has both Read and Write. Read-only tokens cannot provision infrastructure. Ask your agent for help:

Deploy your first app

Credentials ready? Deploy your app