All requests to the LumozAI API require authentication using your secret API key. Pass your key in the standard Authorization HTTP header as a Bearer token.
Submit a synchronous or asynchronous generation job for FLUX 3 Image (flux-3-image). Fast-running image models return the generated asset directly; longer inference pipelines return a request_id for asynchronous polling.
Request parameters for FLUX 3 Image
10 total fields
Parameter
Type
Required
Default
Description / allowed values
model_id
string
Required
flux-3-image
Unique model identifier. Must be set to flux-3-image.
prompt
Prompt
string
Required
—
Text description of the image to generate, or of the edit to apply to reference images.
images
Reference Images
array of URLs
Optional
—
Up to 10 reference images the prompt edits or draws from. When present, runs as an edit and the first image drives 'auto' aspect ratio.
aspect_ratio
Aspect Ratio
enum
Optional
auto
Aspect ratio of the generated image. 'auto' picks the ratio from prompt or first reference image.
The API uses conventional HTTP response codes to indicate success or failure. In general, 2xx indicates success, 4xx indicates client input issues, and 5xx indicates server errors.
Status
Error code
Description
401
authentication_failed
Missing or invalid Authorization Bearer header.
403
permission_denied
Insufficient credits or account tier permissions.
404
model_not_found
The specified model_id does not exist or is deprecated.
422
validation_error
Missing required parameters or invalid parameter types.
429
rate_limit_exceeded
Request rate quota exceeded for your tier.
500
internal_server_error
Downstream GPU compute error or worker timeout.
JSONValidation error example
{
"success": false,
"error": {
"code": "validation_error",
"message": "The model_id field is required.",
"details": {
"model_id": ["The model_id field is required."]
}
}
}
Rate limits
Quota & throughput limits
Rate limits are enforced per API key to guarantee fair access and consistent low latency across GPU workers. Every API response includes informative headers:
Header
Description
X-RateLimit-Limit
Maximum number of requests permitted per rolling hour.
X-RateLimit-Remaining
Number of remaining requests in the active window.
X-RateLimit-Reset
Unix epoch timestamp when the current window refreshes.
Handling 429 status codes
When rate-limited, wait for the number of seconds until X-RateLimit-Reset or implement exponential backoff retries. For custom high-concurrency limits, contact support.
RAG API/api/v1/memory/*
Serverless vector memory & semantic search
Store, index, and retrieve vector embeddings with sub-50ms latency. Unlike traditional vector databases that charge monthly cluster upkeep fees, Lumoz includes 5,000 vector memory slots and 10,000 semantic queries with any active balance.
Core endpoints
Method
Endpoint
Description
GET
/api/v1/memory/usage
Inspect active tier, vector storage meter, and monthly search counters.
POST
/api/v1/memory/projects
Create an isolated project/namespace (e.g. support-bot).
POST
/api/v1/memory/store
Embed and index text documents or knowledge chunks.
POST
/api/v1/memory/search
Cosine similarity search with hybrid keyword weighting.
DELETE
/api/v1/memory/{id}
Delete an indexed memory item.
Code examples
cURLStore knowledge & semantic search
# 1. Ingest text into an isolated namespace
curl -X POST "https://lumozai.com/api/v1/memory/store" -H "Authorization: Bearer YOUR_LUMOZ_API_KEY" -H "Content-Type: application/json" -d '{
"project": "support-bot",
"text": "Refunds are processed within 48 hours to original payment method.",
"metadata": {"category": "billing"}
}'
# 2. Query vector memory via cosine similarity
curl -X POST "https://lumozai.com/api/v1/memory/search" -H "Authorization: Bearer YOUR_LUMOZ_API_KEY" -H "Content-Type: application/json" -d '{
"project": "support-bot",
"query": "How long do refunds take?",
"top_k": 3
}'