Agent report card
Can an agent use DigitalOcean Cloud through API resource management?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayReady
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
DigitalOcean provides public entrypoints and reference documentation for its four primary APIs: DigitalOcean API, Spaces API, OAuth API, and Metadata API.
Applicable terms are stable, readable, retrievable, and materially complete.
Eligibility conditions and required inputs are explicit and decidable.
Price or no-charge status, variables, currency, and material conditions are explicit.
Verified structured artifacts accelerate discovery of the evaluation surface.
Web-agent access policy is explicit and verified for the assessed resources.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
DigitalOcean's terms establish eligibility criteria, including requiring users to be 18 years or older or have legal consent and capacity, and requiring account registration with name, email address, and a valid form of payment.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Pricing rates and variables are explicitly listed across products, such as Inference starting at $0.05/M tokens, GPU Droplets from $1.91/GPU/hour, App Platform starting at $0/month, and Droplets starting at $4/month.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
DigitalOcean provides public entrypoints and reference documentation for its four primary APIs: DigitalOcean API, Spaces API, OAuth API, and Metadata API.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
DigitalOcean explicitly provides a structured documentation index for AI agents at https://docs.digitalocean.com/llms.txt and offers Markdown versions of documentation pages.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
Applicable commitment terms are retrievable and readable via DigitalOcean's Legal Terms of Service Agreement, which incorporates by reference the Data Processing Agreement, Acceptable Use Policy, Privacy Policy, and Service Terms.
Does the vendor deliberately describe access for web agents?
supported: freshWeb-agent access policy is explicit and verified for the assessed resources.
DigitalOcean explicitly directs AI web agents to its structured documentation index at https://docs.digitalocean.com/llms.txt and Markdown page endpoints.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
DigitalOcean provides personal access tokens with custom scopes and expiration settings, but token creation requires logging into the Control Panel and manually generating the token.
A stable canonical route begins the required access bootstrap.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshCurrent admissible evidence does not resolve this finding.
The registration endpoint returned a Cloudflare block page with HTTP status 403. Because this is an error and challenge response, it does not resolve the access control operability finding.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
DigitalOcean documentation explicitly provides a canonical access route directing users who do not have an account to sign up using the DigitalOcean Control Panel or doctl CLI.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The registration targets returned Cloudflare block pages, and the documentation target does not explicitly declare CAPTCHA requirements. Admissible evidence does not resolve whether access requires an unsupported CAPTCHA.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
DigitalOcean provides personal access tokens with custom scopes and expiration settings, but token creation requires logging into the Control Panel and manually generating the token.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The registration endpoint returned a Cloudflare block page, and droplet setup documentation does not address phone verification. The retained evidence does not establish whether phone verification applies or is compatible.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
DigitalOcean discloses flat and usage-based pricing on its pricing page with monthly caps and currency in USD, including automated billing on the first day of each month or upon reaching a threshold.
A documented direct purchase path reaches paid access without a vendor decision point.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
Documentation describes adding payment methods and paying balances, but does not provide details on deterministic checkout construction and handoff resumption for an agent.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
DigitalOcean discloses flat and usage-based pricing on its pricing page with monthly caps and currency in USD, including automated billing on the first day of each month or upon reaching a threshold.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
Docs detail adding credit cards or third-party payment providers to submit payments, but do not state a delegated payment authorization rail for agents.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
DigitalOcean bills monthly for the resources used and documents a self-service payment procedure on the Billing page: choose a saved card, add a new card or use a third-party provider, then Submit Payment. No vendor decision point stands between adding a payment method and paid use.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Personal access tokens can be created in the DigitalOcean Control Panel. DigitalOcean documentation states that when creating a token, users must save the displayed token because the secret is only shown once for security purposes.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
Personal access tokens can be created in the DigitalOcean Control Panel. DigitalOcean documentation states that when creating a token, users must save the displayed token because the secret is only shown once for security purposes.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshCompletion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
When creating a Droplet in the DigitalOcean Control Panel, a progress bar displays how close the Droplet is to being ready. The documentation does not detail asynchronous failure reconciliation, terminal failure states, or explicit bounds.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Droplet provisioning is machine-triggerable and can be initiated directly via the DigitalOcean CLI using `doctl compute droplet create` or via the DigitalOcean API by sending a POST request to `https://api.digitalocean.com/v2/droplets`.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
- Expose bounded machine-readable terminal status and reconciliation semantics.
Safe failure handling is documented only partially.
DigitalOcean documents structured 4xx/5xx errors and rate-limit headers with 429 retry-after; the selected quotes do not establish idempotency, cancellation or reconciliation semantics.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Essential operations have stable readable request, response, and effect semantics.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts describe REST or RPC interfaces, SDKs and CLIs for DigitalOcean Cloud; they contain no first-party statement that an agent-native protocol interface is absent, and several navigation excerpts mention MCP resources without establishing coverage of the assessed targets.
- resource-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Personal access tokens function like passwords, can be generated with custom scopes and specific expirations, and can be deleted if compromised to revoke access or regenerated. However, recovery or automated rotation within delegated authority is not fully documented.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
DigitalOcean documents structured 4xx/5xx errors and rate-limit headers with 429 retry-after; the selected quotes do not establish idempotency, cancellation or reconciliation semantics.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
DigitalOcean API requests authenticate using a personal access token passed as a Bearer token in the Authorization header. Scoped authority is supported via custom CRUD scopes (Create, Read, Update, Delete) mapped to resource types.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
API endpoints, request headers, JSON request/response formats, parameters, and error objects are documented with stable schemas and examples. For Droplet provisioning, required fields (region, size, image) and cURL/SDK request payloads are explicitly defined.
- resource-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Essential management targets are operable programmatically via stable HTTP REST APIs, the official doctl CLI, and official SDKs such as PyDo and Godo.
- resource-api
What would improve this stage
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
- Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
What blocks agents
No stage is established as blocked.
Where autonomy is limited
- Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
What this grade establishes
14 of 14 graded signals have current supporting evidence. 0 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.
How the grade is derived
A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.
Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.
Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.
Startup offers
DigitalOcean on the startup-offers board
- 12 months of cloud credits (amount varies) + 15 months free Standard-tier supportDigitalOcean Startups Program
Distribution
The grade’s badge
One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.
[](https://sourcey.com/log/digitalocean/agent-readiness/digitalocean-cloud/api-resource-management)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4x8r3etq6ck2b79hsw5
- Projection
- sha256:cdb9159c562050d41e541e5cca1140e5869e4acd2a23152b162f9840857e6ccf
- Policy
- service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration