Identity
The product name, operator, official website, and product purpose must be attributable to a public source.
Methodology
textanai separates what a product claims, how a person can reach it, and when that path was last checked. This page explains the standard behind every listing and guide.
The product name, operator, official website, and product purpose must be attributable to a public source.
A listing is labeled as a public number, number after signup, private beta, phone demo, or infrastructure—not simply “available.”
iMessage, SMS, RCS, WhatsApp, phone, Telegram, web, and email are recorded separately.
Listings carry a source-check or public-number verification date when one is available.
Descriptions state the job the agent does rather than repeating broad AI marketing claims.
Operators and readers can submit a current first-party source when a number, channel, or access path changes.
Review workflow
Prefer the official product page, documentation, help center, or first-party launch post.
Record whether a reader can text now, must sign up, or can only join a beta.
Use explicit source language and avoid treating SMS, RCS, and iMessage as interchangeable.
Summarize the specific job, supported access, prompt, and limitations in plain language.
Weight source quality, access clarity, channel evidence, and market signal.
Update the date and source when public information changes; preserve clear provenance.
Editorial guides rank agents for a stated use case. We consider messaging fit, access clarity, source quality, the completeness of the task, and the recency of the public evidence. A product is not “best” simply because it has more integrations or funding.
Sponsored placement, if introduced, must be labeled and kept separate from editorial judgment. The provider map currently has no paid inclusion. Agent listings link to their sources so readers can check the evidence directly.
Confidence is a directory signal, not a product quality score. A high value means the public identity, source, access path, and messaging channel are well supported. It does not guarantee uptime, safety, accuracy, or a successful result.
Founders and operators can claim a listing to provide a current source, correct an access path, or add first-party context. Claims do not automatically override the public evidence. Material changes should be supported by documentation or a product-controlled page.