new-term-radar
Daily radar for new AI terms: names of new models, products and repos, caught on X, Hugging Face, GitHub and sitemaps before keyword tools list them.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Your real product. Studio stages. Every marketplace size.
AI builds the scene around your product. It never redraws the product.
Upload one product photo. Cloudinary cuts out your real product, places it on studio stages generated by 3 different AI models side by side, can optionally relight the scene while locking your original product pixels back on top, and exports a 4-file marketplace kit: Amazon white 2000×2000, Instagram, Story and WhatsApp/Meesho.檢視完整 README ↗Your real product. Studio stages. Every marketplace size.
AI builds the scene around your product. It never redraws the product.
Upload one product photo. Cloudinary cuts out your real product, places it on studio stages generated by 3 different AI models side by side, can optionally relight the scene while locking your original product pixels back on top, and exports a 4-file marketplace kit: Amazon white 2000×2000, Instagram, Story and WhatsApp/Meesho.
Built for Pixels to Products: Cloudinary AI Hackathon 2026 (HackIndia) · Track 2: Generative Content Workflows Runs entirely on Cloudinary's free tier: 50 image-generation credits, $0. Team ConsoleLog · [hackindia-team:pixels-to-products-cloudinary-ai-hackathon-2026:consolelog]
Links: Live demo (live AI on, capped at 15 credits; library stages and the kit keep working after the cap) · Demo video (made in Remotion from the real live run, see video/) · Planning and reviews
One click, four marketplace files (the real kit downloaded in the live demo):
Track 2: Generative Content Workflows. It asks for "Cloudinary AI image generation, including variations and model choice, inside an existing pipeline". RealStage covers both halves:
e_background_removal/e_trim).image_to_image relights the scene._core) are layered back on top. This is Pixel-Lock./v2/generate)next/font, OFL)Cloudinary is the whole backend: there is no database.
| Cloudinary capability | Where | What it does in RealStage |
|---|---|---|
Signed Upload API (direct from browser, overwrite:false, incoming c_limit) | lib/services/cutout.ts, components/api.ts | Uploads phone photos up to 10 MB without passing through Vercel |
Background removal e_background_removal + e_trim | lib/urls.ts CUTOUT_TRANSFORM | One canonical cutout, materialized once as <id>_cut |
| Upload from a derived URL | lib/cloud.ts uploadFromUrl | Materializes cutouts, composites, finals (with 423 retry) |
Image Generation text_to_image with model choice + seed | lib/services/generate.ts, scripts/setup.ts | Library stages and live 3-model fan-out |
Image Generation image_to_image with reference [1] | lib/services/generate.ts | Relight of the composite |
Async generation + tasks endpoint, quota in limits.addons_quota | lib/cloud.ts parseGen | Polling, plus a credit trip-wire from Cloudinary's own counter |
| Upload preset as generation target | scripts/setup.ts (realstage_gen) | Generated assets land in the right folder with tags |
Layers/overlays l_…/fl_layer_apply, o_, c_scale | lib/urls.ts compositeTransforms | Product + contact shadow composited on a stage, pure URL |
Crops, c_pad + b_white, c_limit, e_blur backdrops | lib/urls.ts kitFiles | Amazon white 2000², Instagram, Story, WhatsApp |
fl_attachment:<name> | lib/urls.ts | Named downloads, no archive needed |
f_auto,q_auto | previews everywhere |
Browser ──(1) /api/sign──► budget check ─► signature (fixed params)
│ (2) direct signed upload ───────────────► Cloudinary Upload API
│ (3) /api/cutout ─► e_background_removal/e_trim ─► _cut (+ sharp: coverage, _core)
│ (4) /api/state ─► library stages (tags) · AI budget · samples [snapshot fallback]
│ composites = Cloudinary layer URLs built in lib/urls.ts (0 credits)
│ (5) /api/generate ─► credit slots ─► /v2/generate text_to_image ×3 | image_to_image (Pixel-Lock)
│ (6) /api/kit ─► materialize final ─► 4 fl_attachment URLs ─► white check
└──── Download all (JSZip in the browser) daily cron ─► delete exp- tags (+invalidate)
Measured costs (Cloudinary used_by_request, 1K):
| Model | Credits per image |
|---|---|
| flux-2-klein-9b | 1 |
| nano-banana-1 | 4 |
| recraft-v3 | 4 |
| flux-2-klein-9b-edit (relight) | 3 |
Where the 50 free credits went (Cloudinary's own counter, 1 Oct 2026):
| Use | Credits |
|---|---|
| 8 library stages (Kota stone on 3 models + 5 Flux scenes) | 14 spent |
| Relight bake-off, 3 samples (docs/bakeoff.md) | 9 spent |
| Live demo recording (relight + 3 Flux variations) | 7 spent |
| Left for judges on the live site | 20 (ledger cap 15; live AI pauses at 6 left) |
overwrite:false. Two concurrent requests can never both win a credit.GEN_MODE=mock and spend 0 credits.Requires Node 20+ and a free Cloudinary account.
git clone https://github.com/Guten-Morgen1302/Pixels-to-Products-Cloudinary-AI-Hackathon-2026.git
cd Pixels-to-Products-Cloudinary-AI-Hackathon-2026
npm install
cp .env.example .env.local # fill in CLOUDINARY_URL (Console → Settings → API Keys); generate the two secrets
npm run check:free # free-tier checks, 0 AI credits
npm run setup # shadow asset, upload preset, metadata fields, 3 pre-cut samples (0 AI credits)
npm run setup:generate # library stages, guarded (≤ 20 AI credits; skips anything that already exists)
npm run dev # http://localhost:3000 (GEN_MODE=mock → live AI is simulated, 0 credits)
Production (Vercel):
.env.example, with GEN_MODE=live, LIVE_AI=on, LIVE_UPLOADS=on, SESSION_SECRET and CRON_SECRET.vercel.json.npm test # 70 unit/service tests (network blocked; credit-spending calls impossible)
npm run typecheck
npm run smoke # real-account pipeline: sample → composite → 4 kit downloads → Amazon 2000² white (0 AI credits)
npm run bakeoff # relight calibration on 3 samples (≤ 3 AI credits, guarded)
Manual check (2 minutes):
1-HERO-teapot.jpg). Three stages appear, each with its model and seed.Uploaded photos and everything derived from them carry an exp-<date+7> tag. A daily cron deletes them and purges the CDN.
MIT
| Fast on-screen images (downloads use explicit JPG) |
| Tags + contextual metadata | stages, sessions, exp- expiry | Data layer: stage geometry, model, seed, sessions |
| Structured metadata | lib/services/kit.ts, scripts/setup.ts | rs_product_name, rs_stage_model, rs_alignment, rs_pixel_locked on every final |
Admin API (resources_by_tag, prefix listing, update, usage) | lib/budget.ts, lib/services/stages.ts | Library listing, budget, plan-credit guard |
Create-if-absent (overwrite:false → existing) | lib/budget.ts | Atomic credit ledger with no extra database |
delete_resources_by_tag + invalidate | lib/services/cleanup.ts, daily cron | 7-day deletion promise, CDN purged |