Agent report card
Can an agent use Twilio Messaging API through Message operations?
Grade C+: Only some material eligibility conditions are decidable before commitment.
twilio / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateLimited
- Sign upLimited
- PayReady
- ProvisionLimited
- 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.
Twilio's Terms of Service explicitly define material eligibility conditions including legal power and authority to accept the agreement, entity domicile identification, and representations regarding authority, but specific product-level eligibility criteria are not fully detailed in the provided excerpt.
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.
Twilio provides explicit pay-as-you-go pricing variables for SMS ($0.0083) and WhatsApp ($0.005) messaging, alongside phone number fees ($1.15/month).
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
The Twilio API overview documentation outlines stable REST APIs and SDK entrypoints for the Messaging API.
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.
Applicable terms of service are retrievable and readable, detailing customer responsibilities, acceptable use policy incorporation, and document order of precedence.
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.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
A stable canonical route begins the required access bootstrap.
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 evidence describes Console home page options and trial flows, but does not state whether the access control form inputs, navigation, and validation can be operated deterministically by an agent.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Twilio explicitly provides a stable route to begin obtaining service access by instructing users to sign up for a Twilio trial account, which opens the Twilio Console.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence across both captured targets describes trial setup, phone verification steps, and account options, but does not state whether a CAPTCHA is present or if an agent-compatible route exists.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Twilio supports machine credentials such as API keys (Main, Standard, and Restricted) that can be generated or revoked, but obtaining them via the Console involves manual credential management.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The sign-up process explicitly requires verifying a personal phone number via SMS, but the retained text does not define a supported, resumable handoff mechanism for an agent following human verification.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
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 documentation describes clicking Upgrade in the Twilio Console to create a profile, add an address, load a starting balance, and enter payment details. However, the evidence does not detail deterministic API/protocol flow steps for checkout hand off approval and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Twilio discloses pricing for Messaging API before authorization. It provides a pay-as-you-go model with no contracts or commitments, detailing SMS/RCS starting at $0.0083 per outbound/inbound message plus carrier fees, WhatsApp starting at $0.005 plus Meta template fees, and phone numbers starting at $1.15 per month.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The evidence states that upgrading involves adding payment details and loading a starting balance in the Twilio Console, but it does not specify a documented rail supporting scoped agent 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.
Twilio documents a direct self-service path to move from a free trial to a paid account. Users can click the Trial banner or Upgrade in the Console, create a profile, add an address, load a starting balance, and add payment details to upgrade without a vendor decision point.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
Twilio declares that Standard and Restricted API keys can be created through its REST API, but the retained excerpt does not fully specify secret response and transfer semantics.
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.
The REST API creates Message resources and returns a status property with explicit message states such as queued or sending. Current evidence leaves asynchronous reconciliation and documented bounds unresolved.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Provisioning of outgoing messages can be initiated directly by sending an HTTP POST request to the Account Messages list resource URI.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
- Expose bounded machine-readable terminal status and reconciliation semantics.
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.
Twilio documents that API keys can be used to authenticate requests and can be revoked if compromised or no longer used to prevent unauthorized access. However, full automated credential lifecycle including programmatic rotation or recovery paths for main account secrets is not completely established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Twilio documents API error status codes (e.g., 400 Bad Request, 404 Not Found, 429 Too Many Requests, 500/503), error response structures (status, message, code, more_info), and delivery status callback tracking via MessageStatus and ErrorCode. Complete failure semantics such as explicit idempotency bounds or cancellation guarantees remain partially covered.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Twilio supports request-time authentication using API Key and API Key Secret (recommended) via HTTP Basic authentication, providing standard or restricted fine-grained access permissions across API endpoints.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
The API inputs, outputs, and effects are stably documented across the target resources, including request parameters, JSON/XML response schemas, status codes, HATEOAS URIs, status callback payloads, and CRUD message operations.
- messaging-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
All essential assessment targets are accessible via stable, documented interfaces including REST HTTP APIs, Twilio SDKs across major programming languages, and the Twilio CLI.
- messaging-api
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
- Pay: Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
What blocks agents
- Evaluate: Only some material eligibility conditions are decidable before commitment.
- Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xm8n4vc1f7z6qs2yh5
- Projection
- sha256:c3941dc76f86f1b5e5539a8ccb95cfdad0f8b8303b985d77d1653b8c95ad1248
- 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