Focused server-side examples for building in-context image generation and editing workflows with Flux Kontext on PoYo.
Flux Kontext is useful for scene-preserving edits, product image changes, prompt-driven visual revisions, and image workflows where the input context should remain coherent.
Try on PoYo | Get API Key | Docs | Pricing | Main Examples
- Text-to-image with
flux-kontext-pro - Image editing with
flux-kontext-pro-edit - Higher-detail paths with max variants
- Async task flow with polling and webhooks
- cURL and Node.js backend examples
cp .env.example .env
export POYO_API_KEY="your-api-key"Run the Node.js example:
cd node
npm startKeep POYO_API_KEY on the server. Do not expose it in browser code, mobile apps, screenshots, or public logs.
- Keep
POYO_API_KEYon the server - Submit a generation task
- Store
data.task_id - Poll status while testing
- Use
callback_urlwebhooks in production
This repo uses flux-kontext-pro, flux-kontext-pro-edit, flux-kontext-max, and flux-kontext-max-edit.
| Path | What it covers |
|---|---|
curl/generate.md |
Copy-paste async submit request. |
node/ |
Native Node.js backend example with polling. |
docs/prompt-examples.md |
Practical prompts for product workflows and creative tests. |
docs/production-notes.md |
Security and reliability notes before launch. |
webhooks/express-webhook/ |
Minimal Express receiver for PoYo callbacks. |
make checkOn Windows:
./scripts/check.ps1MIT