Agent report card
Can an agent use Cloudflare Developer Platform through API resource management?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayLimited
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
The Cloudflare API reference documentation explicitly exposes stable entrypoints and methods, such as Upload Worker Module, and lists public API navigation and endpoints.
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.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
The Self-Serve Subscription Agreement explicitly states that entering into the agreement requires authority to bind the entity represented, and that the agreement becomes effective when accepted, accessed, or used.
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.
Cloudflare provides explicit, transparent pricing options in USD for plans including Free ($0/month), Pro ($20/mo billed annually or $25/mo billed monthly), and Business ($200/mo billed annually or $250/mo billed monthly).
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
The Cloudflare API reference documentation explicitly exposes stable entrypoints and methods, such as Upload Worker Module, and lists public API navigation and endpoints.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
Cloudflare explicitly provides machine-readable structured discovery artifacts, including exporting OpenAPI schemas for API operations and pointing to structured documentation files (llms.txt).
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
The complete Self-Serve Subscription Agreement terms governing Cloudflare's Services and APIs are accessible, readable, and retrievable.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
The provided evidence mentions robots.txt rules API endpoints and crawlers in documentation, but does not provide the explicit web-agent access permissions or disallows for the assessed resources.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Cloudflare provides scoped, revocable API tokens with defined permissions, but token secret delivery requires manual user copying from the dashboard.
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 capture at dash.cloudflare.com returned a bot-verification interstitial ('Just a moment... Performing security verification') rather than the sign-up form; the access flow itself was not observed.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable canonical route to access Cloudflare exists at the login documentation page.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The registration capture at dash.cloudflare.com returned a bot-verification interstitial ('Just a moment... Performing security verification') rather than the sign-up form; the access flow itself was not observed.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Cloudflare provides scoped, revocable API tokens with defined permissions, but token secret delivery requires manual user copying from the dashboard.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence does not state whether phone verification is required or optional for account access.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
Documentation establishes self-service management paths to purchase Cloudflare products, add payment methods, or upgrade domain plans in the dashboard, but contract plans for mission-critical applications require custom enterprise billing.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence describes adding primary and additional payment methods in the Cloudflare dashboard, but it does not establish an API, protocol, or web flow for deterministic checkout construction, approval handoff, and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Cloudflare discloses commercial commitments for its plans and products, including free ($0/month), Pro ($20/mo billed annually or $25/mo billed monthly), Business ($200/mo billed annually or $250/mo billed monthly), and Workers usage rates ($0.30 / million requests, $0.02 / million CPU ms).
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
While documentation lists payment methods such as credit cards, PayPal, Apple Pay, Google Pay, and Stripe Link along with 3D Secure authentication, the retained text does not define a payment authorization mechanism with scoped agent delegation or explicit human-confirmed authorization with receipts.
Is a direct self-service path to paid access documented?
supported: freshSelf-service is tier- or condition-limited, or a bounded vendor review exposes status.
Documentation establishes self-service management paths to purchase Cloudflare products, add payment methods, or upgrade domain plans in the dashboard, but contract plans for mission-critical applications require custom enterprise billing.
What would improve this stage
- Document a direct purchase path or bounded vendor review with machine-readable status.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
According to Cloudflare documentation, selecting Create Token generates the token's secret, which must be copied to a secure place by the user and is only shown once. Because access material delivery relies on manual human copying/transfer, it satisfies partial delivery.
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.
According to Cloudflare documentation, selecting Create Token generates the token's secret, which must be copied to a secure place by the user and is only shown once. Because access material delivery relies on manual human copying/transfer, it satisfies partial delivery.
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.
A deployment records which version is actively serving traffic and who created it and when, so an agent can confirm a deployment completed; the tested pages do not document polling, terminal failure states or reconciliation of an asynchronous provisioning failure.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Provisioning and updates can be triggered directly by agents through Cloudflare's API endpoints (such as Workers scripts upload) or CLI tools like Wrangler via 'wrangler deploy'.
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.
Cloudflare troubleshooting documentation states that verifying an API token via /user/tokens/verify returns success status and expiration metadata, but it does not establish full failure mode semantics such as retries, idempotency, or reconciliation.
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 Cloudflare Developer Platform; 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.
Cloudflare API documentation describes creating and verifying API tokens with specific permissions and TTLs, and using the /user/tokens/verify endpoint to check status. Complete agent management of rotation, revocation, compromise response, and recovery is not established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Cloudflare troubleshooting documentation states that verifying an API token via /user/tokens/verify returns success status and expiration metadata, but it does not establish full failure mode semantics such as retries, idempotency, or reconciliation.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Cloudflare API operations authenticate using HTTP Bearer tokens via the Authorization header, which can be verified at the /user/tokens/verify endpoint.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Cloudflare API endpoints provide defined request parameters, response schemas, and rate-limiting headers across troubleshooting, rate limits, and Workers script update resources.
- 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.
Cloudflare provides documented API HTTP interfaces across API troubleshooting, rate limit references, and Workers script update endpoints.
- 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.
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.
- Pay: Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
- 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
Cloudflare on the startup-offers board
- $10,000 in creditsCloudflare for Startups - Tier 3
- $100,000 in creditsCloudflare for Startups - Tier 2
- $350,000 in creditsCloudflare for Startups - Tier 1
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/cloudflare/agent-readiness/cloudflare-developer-platform/api-resource-management)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4x62a9z5fqb4kvp1hme
- Projection
- sha256:7c9aab2e86f70cd6f9a2de83caca999172fb5670938fea3af8cd773340fed4fa
- 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