Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:92590800933b…

Agent report card

Can an agent use OpenAI API through API service lifecycle?

Grade B+: Only part of the applicable terms is machine-readable.

OpenAI / active

Agent ReadinessB+Limited
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Limited

    Only part of the applicable terms is machine-readable.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Eligibility can be decided from explicit public criteria.

    Pricing or the absence of a charge is explicit and machine-readable.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility

    supported: fresh

    Eligibility can be decided from explicit public criteria.

    OpenAI specifies clear public eligibility criteria for accessing its business and developer API services, including geographic restrictions and compliance with applicable trade control laws.

    decidable_eligibility: Ready: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    The product and funnel are machine-discoverable through standard OpenAPI / documentation index endpoints like llms.txt and direct structured API references.

    machine_discovery: Ready: tested 7 Aug

    Method http 1

    Readable pricing

    supported: fresh

    Pricing or the absence of a charge is explicit and machine-readable.

    Pricing per token, cached input, and output across models is clearly published and machine-readable on the public pricing page.

    readable_pricing: Ready: tested 7 Aug

    Method http 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    The OpenAI Services Agreement is publicly accessible as stable HTML and PDF documents, but is not exposed in a fully machine-readable structured data format like JSON-LD.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What would improve this stage

    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Ready

    A stable signup entrypoint is available.

    Machine-operable signup has not been established.

    Whether CAPTCHA blocks signup has not been established.

    Whether phone verification is required has not been established.

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Evidence and actions

    CAPTCHA-free signup unknown

    supported: fresh

    Whether CAPTCHA blocks signup has not been established.

    The captured headless signup page content only contains title metadata and lacks sufficient form details to determine if CAPTCHA blocks signup.

    captcha_free: Unknown: tested 7 Aug

    Method headless 1

    Machine-operable signup unknown

    supported: fresh

    Machine-operable signup has not been established.

    The retained signup evidence consists only of metadata and page titles, providing insufficient detail to verify machine-operable controls.

    machine_operable_form: Unknown: tested 7 Aug

    Method headless 1

    Phone-free signup unknown

    supported: fresh

    Whether phone verification is required has not been established.

    The captured evidence does not reveal the complete signup workflow, leaving it unestablished whether phone verification is required.

    phone_verification_free: Unknown: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    The platform signup HTTP target resolves successfully and provides a stable landing entrypoint for account creation.

    stable_entrypoint: Ready: tested 7 Aug

    Method http 1

    Supported identity flow

    supported: fresh

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Documentation outlines scoped service accounts, API keys created in the dashboard, and workload identity federation across multiple providers with explicit access controls.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

  3. Pay

    Ready

    The required price or no-charge status is explicit before commitment.

    Machine-operable checkout has not been established.

    A supported payment rail has not been established.

    Whether sales intervention is required has not been established.

    Evidence and actions

    Explicit price

    supported: fresh

    The required price or no-charge status is explicit before commitment.

    OpenAI provides explicit pricing for API models, multimodal capabilities, and tools per token or per unit of time.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout unknown

    supported: fresh

    Machine-operable checkout has not been established.

    Retained evidence from the signup endpoint does not provide sufficient details on machine-operable checkout controls.

    machine_operable_checkout: Unknown: tested 7 Aug

    Method headless 1

    Sales-free purchase unknown

    supported: fresh

    Whether sales intervention is required has not been established.

    Evidence from the signup endpoint is insufficient to confirm whether the standard checkout flow requires sales intervention.

    sales_intervention_free: Unknown: tested 7 Aug

    Method headless 1

    Supported payment rail unknown

    supported: fresh

    A supported payment rail has not been established.

    Available evidence on the platform signup page does not establish supported payment rails.

    supported_payment_rail: Unknown: tested 7 Aug

    Method headless 1

  4. Provision

    Ready

    Successful onboarding automatically activates usable access.

    Machine-readable provisioning status has not been established.

    A bounded provisioning delay has not been established.

    Usable credentials or delegated access are delivered through a documented flow.

    Evidence and actions

    Automatic activation

    supported: fresh

    Successful onboarding automatically activates usable access.

    Creating an API key in the dashboard immediately activates access for API invocation.

    automatic_activation: Ready: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    A bounded provisioning delay timeframe is not documented in the provided evidence.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

    Usable credentials or delegated access are delivered through a documented flow.

    API keys are generated and provided directly through the developer platform dashboard.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status unknown

    supported: fresh

    Machine-readable provisioning status has not been established.

    Machine-readable provisioning progress and terminal status transitions are not established in the provided evidence.

    machine_readable_status: Unknown: tested 7 Aug

    Method http 1

  5. Operate

    Ready

    A documented API or tool interface is available for operation.

    An agent protocol interface has not been established.

    Authentication is documented and usable within an agent authorization boundary.

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access

    supported: fresh

    A documented API or tool interface is available for operation.

    OpenAI API provides documented HTTP REST endpoints, official SDKs (Python, Node.js, Go, Java, .NET, Ruby), and WebSocket/WebRTC interfaces for programmatic model interaction and resource administration.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery

    supported: fresh

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    OpenAI API documents recovery strategies including generating new API keys upon invalid credentials or revocation, clearing caches, adjusting spend/rate limits, and handling retries via Retry-After headers and WebSocket reconnects.

    delegated_recovery: Ready: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    OpenAI API documents structured error codes, rate limits, spend limits, and retry guidance such as pacing requests and using Retry-After headers.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    OpenAI API authentication is fully documented and usable via API keys set as system environment variables (OPENAI_API_KEY) and automatically read by the SDKs.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

What works

  • Sign up: A stable signup entrypoint is available.
  • Pay: The required price or no-charge status is explicit before commitment.
  • Provision: Successful onboarding automatically activates usable access.
  • Operate: A documented API or tool interface is available for operation.

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzf0m4xe2b7nt9w4r6dh1q8c
Revision
sha256:92590800933bde5783fc679529b90c64b4e081721fb823ff3892d9c2526bd35b
Projection
sha256:3210b268855938d140df57efca324b1ca5ea7a81875b92e45ce12abeeee059f7
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6