bfl-api

Integrate BFL FLUX API endpoints for image generation, editing, and async retrieval.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/shige1014-dev/backup-OpenMontage --skill bfl-api-shige1014-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bfl-api
Source: https://github.com/shige1014-dev/backup-OpenMontage/tree/main/.agents/skills/bfl-api
Command: npx skills add https://github.com/shige1014-dev/backup-OpenMontage --skill bfl-api-shige1014-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides clear, production-ready guidance and code patterns to integrate with the BFL FLUX API so teams can reliably submit image generation and editing requests, handle asynchronous results, and avoid common pitfalls like expired URLs and rate limits.

Core Features & Use Cases

  • Endpoint & Region Selection: Guidance on choosing global, EU, or US endpoints for residency and failover.
  • Authentication & Key Management: Steps to validate and securely load BFL_API_KEY for CLI, local, and server environments.
  • Async Patterns: Polling strategies, exponential backoff, adaptive polling, and webhook integration with signature verification.
  • Rate Limiting & Retries: Client-side semaphores, queueing, retry/backoff policies, and headers to monitor limits.
  • Error Handling & Resilience: Classification of retryable vs non-retryable errors, circuit breaker pattern, and logging best practices.
  • Use Case: Integrate into server applications or agents to generate or edit images, process batches, and persist results before URL expiration.

Quick Start

Submit a generation request to the appropriate flux endpoint with your BFL_API_KEY, wait for the polling_url to return status Ready, and immediately download the result URL before it expires.

Frequently Asked Questions about bfl-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle BFL FLUX API polling and rate limiting for image generation?

To handle BFL FLUX API polling and rate limiting, use exponential backoff and client-side semaphores to monitor limit headers and queue requests, preventing retries from exceeding concurrent request thresholds.

What's the best way to retrieve asynchronous results from the BFL FLUX API without expired URLs?

Retrieve asynchronous BFL FLUX API results by polling the returned polling_url until status Ready appears, then immediately download the result URL to avoid expiration and persist the generated images locally.

Can I use webhooks instead of polling for BFL FLUX API image generation requests?

Yes, you can use webhooks instead of polling for BFL FLUX API image generation by configuring webhook integration with signature verification to securely receive asynchronous result notifications without continuous polling.

Does the BFL FLUX API support regional endpoints for data residency and failover?

The BFL FLUX API supports regional endpoint selection for data residency and failover, allowing you to choose between global, EU, or US endpoints when submitting image generation and editing requests.

How do I manage BFL_API_KEY authentication securely in server-side applications?

Manage BFL_API_KEY authentication securely by validating and loading the key through environment variables in server-side applications, CLI tools, and agent workflows to prevent exposure in client-side code.

Why do BFL FLUX API requests fail and how do I implement retry strategies?

BFL FLUX API requests fail due to rate limits or server errors, requiring classification of retryable versus non-retryable errors and implementing retry strategies with exponential backoff and circuit breaker patterns.