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

Agent report card

Can an agent use Twilio Messaging API through Message operations?

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

twilio / 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

    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.

    Twilio publishes explicit eligibility terms in its Terms of Service, specifying intended business or professional use and defining entity jurisdiction rules.

    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.

    Twilio Messaging API and usage documentation are machine-discoverable via structured TechArticle schema and documentation entrypoints.

    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.

    Twilio provides explicit, machine-readable pricing rates per channel and message volume on its 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.

    Twilio's Terms of Service are available as stable HTML legal text on its public website.

    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

    Blocked

    No stable signup entrypoint was available.

    The signup flow could not be operated by an agent.

    A CAPTCHA blocks autonomous signup.

    Phone or SMS verification blocks autonomous signup.

    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 signup URL returned an unexpected application error (404 Not Found), blocking CAPTCHA-free autonomous signup.

    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 signup page resulted in an application 404 error, failing to provide machine-operable signup 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 signup could not be completed due to a 404 application error on the signup URL.

    phone_verification_free: Blocked: tested 7 Aug

    Method headless 1

    Stable signup entrypoint unavailable

    supported: fresh

    No stable signup entrypoint was available.

    The signup entrypoint URL returned an unexpected 404 Not Found application error.

    stable_entrypoint: Blocked: tested 7 Aug

    Method http 1

    Supported identity flow

    supported: fresh

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

    Twilio documents scoped and revocable machine identity flows, including API keys (Main, Standard, and Restricted) with clear creation and revocation boundaries.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

    What blocks agents

    • No stable signup entrypoint was available.
    • 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

    • Publish one stable canonical signup entrypoint.
    • 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

    Blocked

    The required checkout cannot be operated by an agent.

    A supported payment rail has not been established.

    Whether sales intervention is required has not been established.

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

    Evidence and actions

    Explicit price

    supported: fresh

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

    Twilio publishes explicit pay-as-you-go pricing for messaging channels, such as SMS starting at $0.0083 to send or receive a message.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout unavailable

    supported: fresh

    The required checkout cannot be operated by an agent.

    The signup and checkout flow URL returned a 404 error during testing, rendering machine-operable checkout unavailable.

    machine_operable_checkout: Blocked: tested 7 Aug

    Method headless 1

    Sales-free purchase unknown

    supported: fresh

    Whether sales intervention is required has not been established.

    The sign-up funnel page encountered a 404 error during testing, preventing verification of whether sales intervention is required.

    sales_intervention_free: Unknown: tested 7 Aug

    Method headless 1

    Supported payment rail unknown

    supported: fresh

    A supported payment rail has not been established.

    The signup and payment entry page returned a 404 error, so payment rails could not be verified in this test run.

    supported_payment_rail: Unknown: tested 7 Aug

    Method headless 1

    What blocks agents

    • The required checkout cannot be operated by an agent.

    What would improve this stage

    • Expose documented, labelled checkout controls or an agent-compatible commerce interface.
  4. Provision

    Ready

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

    A bounded provisioning delay has not been established.

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

    Provisioning does not apply to this funnel.

    Evidence and actions

    Automatic activation not applicable

    supported: fresh

    Provisioning does not apply to this funnel.

    The message-operations scope covers sending, fetching, updating, and deleting individual message resources via the Twilio Messaging API, where explicit provisioning steps do not apply.

    automatic_activation: Not applicable: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    Documentation notes queuing and validity parameters, but does not document an exact bounded provisioning time guarantee for Message resources.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

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

    Twilio provides documented flows to obtain API Keys (Username/Password) via the Console or API, as well as using Account SID and Auth Token.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status

    supported: fresh

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

    Message resource exposes machine-readable statuses (e.g. queued, sending, sent, delivered, failed, undelivered, scheduled, canceled) via API responses and status callback webhooks.

    machine_readable_status: Ready: tested 7 Aug

    Method http 1

  5. Operate

    Limited

    Recovery is available only for some failure modes or requires human intervention.

    An agent protocol interface has not been established.

    A documented API or tool interface is available for operation.

    Authentication is documented and usable within an agent authorization boundary.

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

    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.

    Twilio Messaging API provides a documented REST API and SDK interfaces for sending and managing messages over HTTPS.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery limited

    supported: fresh

    Recovery is available only for some failure modes or requires human intervention.

    Status callbacks support tracking message states and error codes, but recovery handling and message cancellation are limited to specific scenarios like scheduled messages.

    delegated_recovery: Limited: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

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

    The Messaging API documentation outlines message status values, structured error codes, validity periods, and rate limits.

    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 can be authenticated using HTTP Basic Authentication with API Keys and Secrets or Account SID and Auth Token.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

    What would improve this stage

    • Provide delegated credential rotation, revocation, retry, and recovery paths without requiring unrestricted human intervention.

What works

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

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.
  • Sign up: No stable signup entrypoint was available.
  • Pay: The required checkout cannot be operated by an agent.
  • Operate: Recovery is available only for some failure modes or requires human intervention.

Improve the report

Correct it, rerun it, or improve the funnel

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

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_01kzf0m4xm8n4vc1f7z6qs2yh5
Revision
sha256:cae85d58ad7ba8dd6160dcfa1cab95f78564a42d166cb5ba995139e434fa5182
Projection
sha256:16df1cd473f77c65df6fdf7b832a7524b5209066f51b25c95a20c75d8bd1d8db
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6