API قدرتمند حذف پسزمینه برای توسعهدهندگان
حذف پسزمینه پیشرفته با هوش مصنوعی را با API منسجم و انعطافپذیر ما در برنامههای خود ادغام کنید.
دریافت کلید APIیکپارچهسازی بیدردسر
حذف پسزمینه را با چند خط کد در برنامه خود پیادهسازی کنید. API مستند خوب ما و SDK های زبانهای محبوب کار یکپارچهسازی را آسان میکند.
خروجی قابل تنظیم برای برنامههای متنوع
فرآیند حذف پسزمینه را متناسب با نیازهای خود تنظیم کنید. پارامترها را تنظیم کنید، در قالبهای مختلف صادر کنید، و حتی پسزمینهها را برنامهنویسی تعویض کنید.
عملکرد سطح سازمانی
طراحی شده برای مقیاس و سرعت. API ما روزانه میلیونها درخواست را با تأخیر پایین پردازش میکند، اطمینان حاصل میکند که برنامههای شما حتی در بار سنگین پاسخگو باقی میمانند.
باز کردن ویژگیهای جدید در برنامههای خود
کاربران خود را با قابلیتهای پیشرفته ویرایش تصویر توانمند کنید. از پلتفرمهای تجارت الکترونیکی تا برنامههای رسانههای اجتماعی، با API حذف پسزمینه ما امکانات بیپایان است.
ابزارهای پیشنهادی برای توسعهدهندگان
How a small dev تیم shipped a profile-عکس cropper feature in one sprint
A four-person development تیم building a hobby-بازار app needed a profile-عکس feature that turned a user's casual phone shot into a تمیز catalog-grade avatar. The PM wanted it in the بعدی sprint, the طراح wanted on-برند backdrops the user could pick from, and the پلتفرم تیم wanted no new server bills. A traditional integration would have meant a paid API key, a new microservice, and a queue.
The تیم wired the ویرایشگر's in-browser cutout into the existing آپلود کنید flow as a client-side step. The user picks a عکس, the cutout runs locally on their device, the user picks one of three برند-aligned backdrops, and the resulting JPEG goes straight to the same R2 bucket the rest of the آپلود کنید flow uses. No server-side پردازش, no key rotation, no per-request billing. The whole feature shipped in 480 lines of code, including the picker UI and the analytics events.
The feature went live at the end of the sprint, processed 14,000 avatars in the first ماه with no extra infrastructure cost, and dropped the تیم's profile-completion rate from 31 percent to 58 percent because the picker felt like a curated experience instead of an awkward آپلود کنید field. The پلتفرم bill stayed flat. The تیم kept the same pattern in mind for a future محصول-آگهی عکس step.
"We needed an avatar cropper that didn't add a server-side service or a paid API. Wiring the in-browser cutout into our آپلود کنید flow took one sprint and shipped at zero marginal cost per user. The پلتفرم تیم noticed our request graph didn't change."
"I'm the only engineer and I needed a profile-عکس step that didn't pull in a third-party SDK we'd have to babysit forever. A client-side cutout meant I shipped the feature, then forgot درباره it. No keys to rotate, no rate limits, no پشتیبانی tickets six ماهها later."
"Bundling a heavyweight SDK into a starter template makes the whole project feel bloated. The browser-side approach means contributors can fork the template and not need to set up a third-party account. Adoption of the عکس step is up since I switched."
Picks that fit a توسعهدهنده workflow
Common questions for توسعهدهندگان
Is there a stable API for the in-browser cutout, or do I need to embed the ویرایشگر iframe?
The ویرایشگر exposes a small JavaScript surface that you can call from your own page once the model is loaded. The cutout returns a Blob you own, so you can pipe it directly to your existing آپلود کنید pipeline. The model loader handles caching across sessions via the Cache API, so the ثانیه visit is سریع. There is no iframe required and no postMessage handshake, the function is invokable like any other client-side تصویر operation.
What's the cold-start cost of the model on a first-time visitor?
First-load fetches the WASM runtime and the model weights, which together are roughly 30 MB on the wire. A مدرن broadband connection gets that in two or three ثانیه; a slow mobile network closer to ten. Subsequent visits hit the Cache API and start instantly. For latency-sensitive apps, a preload hint in the HTML head warms the cache before the user reaches the عکس step. Server-assisted fallback is available for devices that can't run the model locally.
Are there usage limits or quotas if I integrate this into a commercial محصول?
The browser-side pipeline runs on the user's device, so there is no per-request quota and no rate limit to negotiate. Server-assisted fallback for the rare device that cannot run the model locally has its own quota documented separately. For high-volume commercial integrations the recommendation is to handle the local-cutout path as the default and surface server fallback only on capability detection failure, which keeps cost predictable as you scale.
Ship a عکس feature without adding a service
Wire the in-browser cutout into your existing آپلود کنید component, keep the فایل on the user's device, and pipe the نتیجه straight to your storage.