Apidot Flux Kontext Api

APIDot Flux Kontext API

Use APIDot as a Flux Kontext-focused API surface for context-aware image generation, single-image editing, character consistency workflows, local edits, typography-aware visual updates, polling, and webhook delivery.

This skill is for routing Flux Kontext questions to the right APIDot docs, model pages, reference notes, and async integration guidance. It is documentation-only: it includes no scripts, makes no network requests, and does not store credentials.

This release contains SKILL.md plus non-executable notes in references/api.md. It includes no executable files, install-time automation, review automation helpers, bundled API clients, automatic network calls, or stored credentials.

Start on APIDot

Use these APIDot entry points when coming from ClawHub:

• Open the Flux Kontext model page: https://apidot.ai/models/flux-kontext
• Read Flux Kontext API docs: https://apidot.ai/docs/flux-kontext
• Open the account dashboard: https://apidot.ai/dashboard/api-key
• Use general APIDot examples: https://github.com/APIDotAI/apidot-examples

When To Use

Use this skill when the user asks to:

• Build a Flux Kontext API integration with APIDot.
• Generate images from prompts, design prompts, product briefs, or campaign concepts.
• Edit images while preserving context, characters, typography, or local visual intent.
• Use Flux Kontext Pro or Flux Kontext Max through APIDot.
• Implement APIDot async image jobs with task submission, task status polling, or webhook callbacks.
• Find APIDot Flux Kontext docs, model pages, or examples.

Security Rules

• Treat APIDOT_API_KEY as a secret.
• Keep APIDot API keys in server-side environment variables or a backend secret manager.
• Never place an API key in browser code, frontend bundles, public repos, logs, screenshots, or chat output.
• Do not make live API calls unless the user explicitly asks and provides a safe server-side environment.
• Do not invent API facts, commercial terms, model availability, reliability claims, performance claims, or competitor comparisons.
• Use current APIDot docs and model pages for model-specific request fields and current product details.

Flux Kontext Workflow

APIDot Flux Kontext generation follows the shared async task pattern:

1. Choose the Flux Kontext request mode from the current APIDot docs.
2. Submit the generation or edit request through the documented APIDot async generation flow.
3. Save the returned data.task_id immediately.
4. Poll task status with the documented task status API for local tests.
5. Use callback_url webhook delivery for production queues or user workflows that may outlive the current page.
6. Store final image URLs only after the task reaches a terminal success state.

Do not guess model-specific payload fields. If the user needs copyable request examples, point them to the current APIDot docs or general APIDot examples.

Model Routing

Start from the user's Flux Kontext task, then open the matching APIDot source:

Use references/api.md for a local, non-executable summary of Flux Kontext model routing, request planning, and async workflow notes.

For Flux Kontext request modes, prefer the live APIDot model page and docs page. Do not copy request fields from another image model family unless the APIDot docs show the same field.

Integration Guidance

• Use apidot-image-generation-api when the user needs broad image generation guidance across several model families.
• Use apidot-flux-2-api when the user specifically needs FLUX.2 workflows.
• Use this skill when the user is specifically building with Flux Kontext through APIDot.
• Ask which image task the user needs before choosing a model-specific example: prompt-only generation, single-image editing, character consistency, local edit, product visual, typography update, or reference-guided generation.
• Persist task_id, selected model, user ID, source media references, request status, and final image URLs together.
• Validate source image URLs before submitting workflows that depend on reference images.
• Treat webhook handlers as idempotent. Duplicate callback deliveries should not create duplicate visible results.
• Retry transient network failures with backoff. Do not retry invalid payloads unchanged.
• Avoid logging API keys, private prompts, private image URLs, generated image URLs, or callback URLs.

Official Links

• Website: https://apidot.ai
• Docs: https://apidot.ai/docs
• Flux Kontext model page: https://apidot.ai/models/flux-kontext
• Flux Kontext docs: https://apidot.ai/docs/flux-kontext
• Quickstart: https://apidot.ai/docs/quickstart
• Webhooks: https://apidot.ai/docs/webhooks
• API key dashboard: https://apidot.ai/dashboard/api-key
• Main examples: https://github.com/APIDotAI/apidot-examples
• GitHub organization: https://github.com/APIDotAI
• Support: support@apidot.ai