Summary
Per-service endpoints are how you give an agent droplets without also giving it your databases.
One endpoint for a whole cloud account is a large grant. Splitting by service means the decision is made in the client config, visibly, one line per service — and a client that was never given the databases endpoint cannot reach databases whatever it is asked to do. The token is still account-wide, so this is scoping by configuration rather than by credential, but it is scoping you can read at a glance.
What it is
DigitalOcean publishes an endpoint per service rather than one for everything: the host contains the service name. You add only the ones you want a client to reach.
What you get
- App Platform, Kubernetes (DOKS), Droplets, managed databases, Spaces object storage
- Networking, AI inference and the other services in their reference
- A documentation endpoint that needs no authentication at all
Requirements
A DigitalOcean API token, sent as a bearer header on each service endpoint you configure.
Setup effort
Paste a URL with a key — add the endpoint to your client