Compare evolving online services

Use when

Compare two or more online services whose features, pricing, access rules, models, or content policies change frequently.

Procedure

1. Convert the request into explicit axes before searching: usability, available models/providers, creation features, policy limits, age/access rules, pricing, and best-fit user.
2. Build a source bundle for each service:
   • official product/help pages for features;
   • official terms or content rules for restrictions;
   • official pricing or current storefront listing for cost;
   • recent reputable reporting only when official pages omit operational details.
3. Search one service and one axis at a time. Prefer narrow official-domain queries over broad result dumps.
4. Record each decisive claim with source date and scope. Separate:
   • platform minimum age;
   • feature- or mode-specific minimum age;
   • storefront content rating;
   • text rules versus avatar/image rules;
   • base access versus paid models, credits, subscriptions, or external API costs.
5. If a dynamic page yields no useful extracted text, stop retrying the same fetch. Use an indexed official result, a direct policy page, or a dated reputable secondary source, and label the source class.
6. Resolve conflicts by preferring the newest applicable first-party source. Treat old launch announcements, reviews, and storefront copy as historical when current terms or pricing disagree. State unresolved conflicts instead of blending them.
7. Draft a compact comparison by axis. End with recommendations tied to distinct user priorities, not a universal winner.

Pitfalls

• Broad multi-topic searches create truncated output and bury decisive evidence.
• “Free” may describe base chat while premium models, image generation, subscriptions, or external APIs still cost money.
• Platform age, adult-mode age, and app-store rating are different claims.
• Marketing copy and launch-era listings can survive after pricing or features change.
• A permissive adult mode does not imply unlimited content; quote the applicable policy scope.

Verification

Before answering, inspect every conclusion-driving sentence. Confirm it has a current source, the correct product and feature scope, and no contradiction with a newer first-party page. Open the final cited links or verify their indexed snippets support the exact claims. Mark any remaining unknown or time-sensitive detail explicitly.