Agent report card
Can an agent use Anthropic API through API service lifecycle?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateLimited
- Sign upReady
- PayReady
- ProvisionReady
- OperateLimited
Only some material eligibility conditions are decidable before commitment.
The exact service and stable evaluation or access entrypoints are publicly discoverable.
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.
Anthropic's Commercial Terms identify governed users and material restrictions, but the retained evidence does not make every service-access condition decidable before commitment.
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 documentation explicitly details the billing structure, variables, currency (USD), CCU conversion rates ($0.01 per CCU), metering cadence, and payment models for the Claude platform and 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.
Anthropic provides public documentation for the Claude API, detailing stable tools including the ant CLI, client SDKs (Python, TypeScript, C#, Go, Java, PHP, Ruby), and a link to the full API reference.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
The applicable Commercial Terms of Service for Anthropic API offerings are retrievable, readable, and materially complete, incorporating the Usage Policy, Supported Regions Policy, Service Specific Terms, DPA, and Model Pricing Page.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
What would improve this stage
- State every material eligibility condition and required input explicitly.
A stable canonical route begins the required access bootstrap.
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 retained page displays sign-in navigation and links to the console, but does not provide access control forms or validation state to evaluate deterministic operability.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable entrypoint is established by the Sign In page displaying options for 'Console login' and 'Log in'.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The evaluated public entrypoints do not expose a CAPTCHA, but the retained non-consequential capture does not establish the complete access flow or a verified-agent alternative.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
The Claude API supports scoped programmatic authorization via API keys or short-lived Bearer access tokens obtained through Workload Identity Federation using POST /v1/oauth/token.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence does not mention phone verification requirements or supported resumable handoffs.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
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.
The retained evidence describes buying prepaid usage credits and configuring auto-reload within the Console settings, but it does not establish deterministic checkout construction, handoff approval, or automated resumption mechanics for an agent.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Anthropic discloses its pricing commitments for Claude Platform on AWS, detailing the $0.01 per CCU billing unit price, hourly metering billing cadence to AWS Marketplace, and postpaid payment model.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The evidence outlines options for updating Console payment card details or paying Stripe invoices, but it does not document a delegated payment authority rail or explicit human-confirmed authorization workflow 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.
Anthropic documents a self-service purchase path for Claude API access where Console users with Admin or Billing roles can directly buy prepaid usage credits under Settings > Billing without a vendor decision point.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Credentials, grants, or configuration are delivered through a documented agent-usable flow.
A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
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.
A documented Workload Identity Federation token endpoint returns short-lived bearer access material programmatically.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshA synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Creating a message via the Messages API is a synchronous request that directly returns a created message object containing a usable result, identifier, and execution usage.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Message creation can be initiated programmatically via direct model prompting using supported SDKs and API calls like anthropic.Anthropic().messages.create().
Safe failure handling is documented only partially.
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?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
The retained documentation lists API lifecycle operations including POST /v1/oauth/token for obtaining short-lived access tokens, alongside Console management and API key usage. However, full programmatically actionable credential rotation, revocation, compromise handling, and recovery procedures are not fully detailed in the provided body text.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Anthropic documents errors, timeouts, and retry guidance, but not complete idempotency, cancellation, and reconciliation semantics for the assessed operations.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Operations are authenticated using either the x-api-key header or the Authorization header with a Bearer token obtained via Workload Identity Federation from POST /v1/oauth/token, alongside the required anthropic-version header.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Essential API operations across Messages, Batches, Files, and Managed Agents have stable, decidable request and response formats, JSON error shapes, request size limits, and rate limit header feedback documented across resources.
- api-service
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
The Claude API provides documented machine-operable interfaces including direct REST API endpoints, the ant command-line tool (CLI), and official client SDKs across Python, TypeScript, C#, Go, Java, PHP, and Ruby.
- api-service
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
- Sign up: A stable canonical route begins the required access bootstrap.
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
- Provision: Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
What blocks agents
- Evaluate: Only some material eligibility conditions are decidable before commitment.
- Operate: Safe failure handling is documented only partially.
Startup offers
Anthropic on the startup-offers board
- API credits and priority rate limitsClaude for Startups Program Credits and Priority Rate Limits
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4x54qzpnr923g24x6x8
- Projection
- sha256:85fb2d56885bd9af74392fea9d3a9730fea895dad2fd43f51744694384e6593d
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration