AI 产品解读Save and extract recipes from any webpage using AI
Users who find recipes on messy web pages want a clean, structured way to save them without manually copying/pasting and reformatting
1. User navigates to a recipe webpage → 2. Clicks extension icon or right-clicks selected text → 3. Content script scrapes page text (excluding nav, ads, sidebars, etc.) → 4. Extracted text is POSTed to recipesaverai.com API with a secret key → 5. Server processes recipe with AI → 6. Popup shows 'Recipe Saved!' with a link to view it on the web service. If extraction fails, a manual paste textarea is shown as fallback.
One-click recipe extraction from current webpage via extension iconRight-click context menu to extract recipe from selected textManual paste fallback when automatic extraction fails (e.g., site blocks scraping)AI-powered recipe parsing sent to recipesaverai.com serverSaved recipes accessible via link on the web service
- 目标用户
- Home cooks who browse recipe websites / Users who want to collect and organize recipes from various sources
- Cannot verify whether the recipesaverai.com API enforces user authentication for the /recipes POST endpoint (uses hardcoded secret key, not user token)
- Cannot verify the destination service's paid plan structure from extension code alone
- The extension communicates only with its own domain (recipesaverai.com) - no third-party analytics or tracking detected
付费分析未识别到付费功能
No payment platforms, billing APIs, subscription logic, upgrade prompts, or premium feature gating found in the source code. All 'pro' keyword hits are false positives (substring matches in 'product' within locale description strings). The extension appears to be entirely free.
- 置信度
- 85
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 是
- 登录理由
- On first install, the extension automatically opens recipesaverai.com/login?intro=true (background.js line 74-75), directing users to sign up on the destination service. Recipes are saved server-side and linked via recipesaverai.com/recipe/{id}. The API call uses a hardcoded secret key (not user auth tokens), but the full workflow (save + view recipes) depends on the web service account.