Aiimagetoprompt vs Tarotai Chat

Free with no paid tier for this tool: the homepage, FAQ, Terms and llms.txt all state no account, no download and no credit card. The site's /pricing route belongs to a different product - the ShipAny SaaS boilerplate - and lists Starter $99/month ($89/month billed annually) for 100 credits, Standard $199 ($169) for 200 and Premium $299 ($249) for 300, each with a 'Get ShipAny' button and bundling a NextJS starter kit, Supabase storage and Vercel deploy; /zh/pricing repeats the same ladder in Chinese. Nothing on the site charges for prompt generation, and /refund-policy returns 404 because there is no transaction. Verified 2026-11-12.

Submitted via form by the vendor 2026-11-12 10:00 UTC; editorial entry written independently from live pages on the site's Pacific working date 2026-11-12 (the mail's UTC date and the working date agree). The submission's name, category (Creative) and summary were accurate, including its own caveat that the tool does not retrieve the original hidden prompt; it supplied no pricing_url or docs_url, which is consistent with the product having no price. Read-only verification, all fetched with a browser user agent: / , /pricing, /zh, /zh/pricing, /privacy-policy, /terms-of-service, /llms.txt, /sitemap.xml, /docs, /robots.txt, /api/generate. Key finding, reproduced in both language mirrors: /pricing (200) and /zh/pricing (200) are unreplaced ShipAny boilerplate - the English page's body reads 'Get all features of ShipAny, Ship your AI SaaS startups fast' with Starter $99/$89, Standard $199/$169 and Premium $299/$249 per month, while the page <title> is still 'Image to Prompt Generator - Convert Images to AI Prompts' - and /docs (200) is ShipAny's 'An AI SaaS development framework based on NextJS' documentation. Neither route is linked from the nav, the footer or the sitemap (sitemap carries only /, /zh, /privacy-policy, /terms-of-service), so they are leftovers rather than an offer, but they serve 200 and are indexable; the same boilerplate leaves /api/get-user-info and /api/update-invite exposed. Trackers read from the served markup: GA4 G-LEMFVNKE14 via googletagmanager on /, /pricing and /docs, and the Cloudflare beacon on every page - while the privacy policy states 'We use essential cookies only' and 'We do not use tracking or advertising cookies', and no consent banner or cookie string renders anywhere. Legal set: /privacy-policy and /terms-of-service both 200 dated 'Effective Date: July 15, 2026' (domain registered 2026-07-05, so the date is plausible rather than pre-dated); they name kie.ai as the AI processing provider and Cloudflare as infrastructure, give retention as periods (images deleted after generation, logs 30 days, prompts in browser local storage), state that the user retains rights to uploads and generated prompts, and require the user to hold rights to uploaded images. Absent: any company name, registration number, postal address or named controller, and any jurisdiction - the governing-law clause reads only 'applicable laws, without regard to conflict of law provisions'. The only published address is a personal Gmail (phamhungfalcon787133@gmail.com) in both documents, which differs from the contact@aiimagetoprompt.org on the submission form. Contact probe: aiimagetoprompt.org publishes a Cloudflare Email Routing MX (route2/route3.mx.cloudflare.net) that answers 250 to contact@, to a plus-addressed variant and to a random local part alike - the domain is a catch-all, so the probe cannot confirm a human reads that mailbox; record it as the best available route, not as a verified one. Reputation/name: 'image to prompt' is a generic descriptor, and the family is crowded with separately operated tools (picsart.com/image-to-prompt, imagetoprompt.dev, imagetoprompts.io, imagetoprompt.me, gocrazy.ai, describeimage.ai, pixelpanda.ai, howtoai.com), so this is not brand-squatting and no rights question arises; aiimagetoprompt.org was registered 2026-07-05 through Dynadot on the Cloudflare NS pair audrey/sid, which matches no cluster in the hold ledger, and neither the Gmail contact nor the ShipAny build matches a held operator (the only other ShipAny builds in the ledger are aihotellobby.dev and three alan/beth siblings, all on different NS pairs, and none of them serve a ShipAny pricing page). Liveness: POST /api/generate returns 400 {"error":"no_image"} for an empty body, so the generation route exists and validates input; no generation was run, so output quality, the advertised Fast/Advance detail levels and the eight output languages are recorded as vendor-stated rather than tested. No affiliate or partner surface exists (/affiliates, /affiliate and /api/affiliate all 404), and no affiliate URL was invented. Published at 3.2/5 - job fit 3.9, transparency 3.2 - below every other tool in the catalog because the site's own pricing route sells a different product and its privacy promise is contradicted by a live tag manager.

One-time packs that never expire: $2.99 for 120 credits, $5.99 for 360, $10.99 for 900. Monthly subscriptions: $3.99 for 800 credits, $9.90 for 3,000 (no rollover, cancel anytime). Credit cost per action is published: single card 10, three-card 20, two-paths 30, Celtic Cross 40, first follow-up free and later follow-ups 5. Stripe is named as the processor.

Submitted via form by the vendor 2026-10-20 (14:22 UTC), category 'Creative' (accurate). Editorial entry written independently. One of four products from the same operator, confirmed in writing 2026-10-20 15:34 UTC; the same reply supplied the inference path (WaveSpeed, google/gemini-3.7-flash) and the session-record retention mechanics. Held on an unnamed contracting party and a GA4 claim that does not match its configuration. Re-verified live 2026-10-21: /privacy-policy (dated 2026-09-27) still reads 'We use self-hosted Umami and Google Analytics 4 ... load by default without requiring click consent', no G- measurement ID appears in any served page, and the shipped config carries an empty gaId. PUBLISHED 2026-10-21 with 'no registered company, trading name, postal address or controller identity' and the GA4/gaId mismatch recorded as stated limitations in cons rather than as a gate. Governing law (Hong Kong) and the provider/model disclosure are credited in pros.