Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:1700725a342b…

Agent report card

Can an agent use Stripe Payments API through API payment lifecycle?

Grade D: Eligibility depends on information or judgment unavailable to an agent.

Stripe / active

Agent ReadinessDBlocked
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

    Blocked

    Eligibility depends on information or judgment unavailable to an agent.

    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.

    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 unavailable

    supported: fresh

    Eligibility depends on information or judgment unavailable to an agent.

    Eligibility criteria depend on Stripe's evaluation and Prohibited or Restricted Business determinations, which cannot be fully decided by an agent from explicit public criteria alone.

    decidable_eligibility: Blocked: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

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

    The Stripe Payments API and core resources are machine-discoverable through the public REST API reference documentation.

    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.

    Stripe provides explicit and structured pay-as-you-go pricing breakdown on its 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 Stripe Services Agreement terms are published as accessible HTML legal pages rather than a fully structured machine-readable format.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What blocks agents

    • Eligibility depends on information or judgment unavailable to an agent.

    What would improve this stage

    • Publish complete, explicit eligibility criteria and required inputs.
    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Blocked

    The signup flow could not be operated by an agent.

    A CAPTCHA blocks autonomous signup.

    Phone or SMS verification blocks autonomous signup.

    A stable signup entrypoint is available.

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

    Evidence and actions

    CAPTCHA-free signup unavailable

    supported: fresh

    A CAPTCHA blocks autonomous signup.

    The headless signup flow hit an incompatible browser barrier, preventing verification of CAPTCHA behavior during registration.

    captcha_free: Blocked: tested 7 Aug

    Method headless 1

    Machine-operable signup unavailable

    supported: fresh

    The signup flow could not be operated by an agent.

    The headless registration page renders an incompatible browser error instead of accessible signup form controls.

    machine_operable_form: Blocked: tested 7 Aug

    Method headless 1

    Phone-free signup unavailable

    supported: fresh

    Phone or SMS verification blocks autonomous signup.

    Autonomous sign up could not proceed because the headless flow was blocked by an incompatible browser page.

    phone_verification_free: Blocked: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    The signup registration endpoint is stable and reachable over HTTP with a canonical URL.

    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.

    Stripe documents a scoped, revocable machine identity flow using restricted API keys with granular permissions alongside secret keys created in the dashboard.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

    What blocks agents

    • The signup flow could not be operated by an agent.
    • A CAPTCHA blocks autonomous signup.
    • Phone or SMS verification blocks autonomous signup.

    What would improve this stage

    • Expose labelled, deterministic controls and documented validation without requiring hidden human interaction.
    • Provide a documented agent-safe verification path that does not require solving a CAPTCHA.
    • Offer a documented verification path that does not require a human-controlled phone or SMS code.

  3. Pay

    Ready

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

    The tested funnel can complete without sales intervention.

    Evidence establishes that this funnel has no checkout step.

    Evidence establishes that this funnel has no payment step.

    Evidence and actions

    Explicit price

    supported: fresh

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

    Stripe's pricing page explicitly outlines pay-as-you-go processing rates (e.g., 1.7% + A$0.30 for domestic cards) with no setup or monthly fees.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout not applicable

    supported: fresh

    Evidence establishes that this funnel has no checkout step.

    The API payment lifecycle for Stripe Payments API does not include a service-level checkout step; billing occurs pay-as-you-go per transaction.

    machine_operable_checkout: Not applicable: tested 7 Aug

    Method headless 1

    Sales-free purchase

    supported: fresh

    The tested funnel can complete without sales intervention.

    Account registration and API access can be completed self-serve online without sales intervention.

    sales_intervention_free: Ready: tested 7 Aug

    Method headless 1

    Supported payment rail not applicable

    supported: fresh

    Evidence establishes that this funnel has no payment step.

    The service API lifecycle operates on pay-as-you-go transactional deduction and does not require a separate payment rail for account checkout.

    supported_payment_rail: Not applicable: tested 7 Aug

    Method headless 1

  4. Provision

    Ready

    Successful onboarding automatically activates usable access.

    A bounded provisioning delay has not been established.

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

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Evidence and actions

    Automatic activation

    supported: fresh

    Successful onboarding automatically activates usable access.

    Stripe provides test API keys and sandboxes for immediate integration testing without manual vendor intervention.

    automatic_activation: Ready: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    The documentation does not specify an explicit bounded delay time guarantee for provisioning completion.

    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 delivered and managed via the Stripe Dashboard for authenticating API requests.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status

    supported: fresh

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Stripe API returns structured, machine-readable HTTP response codes and error type objects.

    machine_readable_status: Ready: 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.

    Stripe Payments API provides a fully documented REST API interface for managing payments, customers, charges, and payment intents over HTTPS.

    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.

    Idempotent requests allow automated retry and recovery from connection errors without duplicating operations by passing an Idempotency-Key header.

    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.

    Stripe documents HTTP response codes, structured error types, idempotency errors, and rate-limiting status codes like 429 with exponential backoff recommendations.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    API requests are authenticated using HTTP basic authentication with API keys (secret keys or restricted API keys) sent over HTTPS.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

What works

  • 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: Eligibility depends on information or judgment unavailable to an agent.
  • Sign up: The signup flow could not be operated by an agent.

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_01kzf0m4xk6m1tb8d5y3pr9wg2
Revision
sha256:1700725a342b1b59e0ab22ef77e1abd030f10e50d3fbde73a285162a1bf07972
Projection
sha256:84a612f7a3bf9fa7fdb43b8c492e8df1b791d5a3ce8852924cefd072147b5519
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6