Agent report card
Can an agent use AWS Cloud through API resource management?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upReady
- PayReady
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
AWS Cloud Control API is publicly discoverable as a standardized API service for performing CRUD-L operations on supported resources in an AWS account, accessible via the AWS Command Line Interface (AWS CLI).
Only some material eligibility conditions are decidable before commitment.
Applicable terms are stable, readable, retrievable, and materially complete.
Price or no-charge status, variables, currency, and material conditions are explicit.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshOnly some material eligibility conditions are decidable before commitment.
AWS Service Terms state specific eligibility requirements for accounts, such as AWS UK Switching Addendum for Eligible Accounts, and explicit eligibility requirements for AWS GovCloud (US) Regions including accurate registration information, but general eligibility requirements across all services are not fully detailed in the provided text.
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.
AWS provides explicit pricing information including a pay-as-you-go model with no long-term contracts, tiered volume-based discounts where usage increases reduce cost per GB, free data transfer IN, and programmatic access to product pricing and Free Tier catalog via the AWS Price List API.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
AWS Cloud Control API is publicly discoverable as a standardized API service for performing CRUD-L operations on supported resources in an AWS account, accessible via the AWS Command Line Interface (AWS CLI).
Are verified structured discovery artifacts available?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts for AWS Cloud are human documentation pages; they contain no first-party statement that structured discovery artifacts are absent, and no artifact was captured or verified either way.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
Applicable AWS Service Terms are retrievable, stable, and readable online via Amazon Web Services, Inc.
Does the vendor deliberately describe access for web agents?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts for AWS Cloud do not state a web-agent or crawler access policy for the assessed resources in either direction.
A stable canonical route begins the required access bootstrap.
AWS provides a stable canonical signup entrypoint allowing users to enter a root user email address and account name to begin account registration.
Scoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
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 signup endpoint displays email and account name fields with a verify email button, but retained evidence does not establish complete access-control operability, validation, and safe handoffs.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
AWS provides a stable canonical signup entrypoint allowing users to enter a root user email address and account name to begin account registration.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
Retained evidence across all evaluated targets does not explicitly state whether CAPTCHA challenges are required or provide an agent-compatible alternative.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
AWS STS supports requesting temporary security credentials using AssumeRole or AssumeRoleWithWebIdentity (OIDC), providing scoped, revocable credentials with explicit consent boundaries.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
Documentation indicates that identity confirmation via phone SMS verification is required, but it does not establish a safe explicit resumable handoff for an agent.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
The evidence discloses AWS's pay-as-you-go pricing approach without requiring long-term contracts, alongside the availability of a catalog of products and prices via the AWS Price List API.
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.
Current admissible evidence does not establish an API 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.
The evidence discloses AWS's pay-as-you-go pricing approach without requiring long-term contracts, alongside the availability of a catalog of products and prices via the AWS Price List API.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
Current admissible evidence indicates a payment method is required to sign up or open an AWS account, but it does not detail a rail supporting scoped delegation or explicit human-confirmed authorization with receipts.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
A direct self-service sign-up procedure is documented where users enter contact/billing information, choose an account/support plan, and complete activation without requiring a vendor decision point.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
AWS Cloud Control API provides progress tracking via get-resource-request-status, returning ProgressEvent objects with OperationStatus (e.g., IN_PROGRESS, SUCCESS) and RequestToken. However, explicit failure reconciliation contracts or explicit time bounds are not fully established in the retained text.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Credentials, grants, or configuration are delivered through a documented agent-usable flow.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshCredentials, grants, or configuration are delivered through a documented agent-usable flow.
The AWS STS API operations return temporary security credentials programmatically, which include an access key ID, a secret key, and a session token.
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.
AWS Cloud Control API provides progress tracking via get-resource-request-status, returning ProgressEvent objects with OperationStatus (e.g., IN_PROGRESS, SUCCESS) and RequestToken. However, explicit failure reconciliation contracts or explicit time bounds are not fully established in the retained text.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Provisioning can be initiated within standard programmatic authority using the CreateResource API call or create-resource AWS CLI command.
What would improve this stage
- Expose bounded machine-readable terminal status and reconciliation semantics.
Safe failure handling is documented only partially.
AWS Cloud Control API documents idempotent ClientToken requests, handler error codes and request status tracking through ProgressEvent; the selected quotes do not establish cancellation semantics for a resource request.
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 AWS 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.
- cloud-control
- public-pricing
- workload-authentication
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
AWS STS documentation explicitly details requesting temporary security credentials with defined expiry durations (DurationSeconds parameter between 15 minutes and 36 hours) and session policies. However, full credential lifecycle management including rotation, revocation, compromise response, and recovery procedures across all credential types is not fully established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
AWS Cloud Control API documents idempotent ClientToken requests, handler error codes and request status tracking through ProgressEvent; the selected quotes do not establish cancellation semantics for a resource request.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
AWS STS documentation explicitly describes requesting temporary security credentials (access key ID, secret access key, and session token) via AssumeRole, GetSessionToken, and federated identity calls to authenticate service operations under scoped permissions.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Across all evaluated assessment targets, essential operation inputs, outputs, schemas, HTTPS endpoints, CLI commands, and pay-as-you-go pricing models are clearly documented with stable, decidable request and response semantics.
- cloud-control
- public-pricing
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Every essential target surface—including Cloud Control API CRUD-L operations, request status tracking, regional endpoints, Price List APIs, and pricing documentation—has documented, usable machine interfaces available through REST APIs, language-specific AWS SDKs, and the AWS CLI.
- cloud-control
- public-pricing
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.
- Sign up: A stable canonical route begins the required access bootstrap.
- 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
- Provision: Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
- 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
AWS on the startup-offers board
- Up to $200,000 in AWS creditsAWS Activate Portfolio credits
- Up to $200,000 in AWS Activate creditsAWS Activate Credits
- Up to $5,000 in AWS credits for selected Founders participantsAWS Activate Founders
- More than $200,000 in AWS creditsAWS credits for AI startups
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/aws/agent-readiness/aws-cloud/api-resource-management)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzez1rxy9f1wce0r3p6yd35y
- Projection
- sha256:812d15400a8fa09f9b14c039320a0db139736ff63240cae4dcee57697543a12f
- 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