fal Platform APIs

Name: fal Platform APIs
Brand: fal Platform APIs
Availability: InStock

✓ Official Vendor SpecAI/MLMl InferenceapiKey32 EndpointsREST

For Agents

Discover hosted generative AI models on fal, estimate pricing, run inference through the serverless queue, and inspect usage and analytics. Useful for image, video, and audio generation flows.

Install Jentic One Beta

Connect the fal Platform APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the fal Platform APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with fal Platform APIs.

List models available on the fal platform with their pricing

Estimate the cost of a model call before submitting it

Submit a generative inference request to the serverless app queue

GET STARTED

Start building with fal Platform APIs

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use fal Platform APIs for, with concrete tasks.

★ Generative Image Inference

An application generates product images on demand by submitting prompts to a hosted diffusion model on fal. The flow lists available models via /models, optionally estimates cost via /models/pricing/estimate, and submits the request to the serverless app queue. Returns generated assets without the team running any GPU infrastructure.

Call GET /models to find a suitable image model, POST the prompt to /models/pricing/estimate to confirm cost, then submit the inference request to the serverless app queue and poll for the generated asset.

Workflow Chaining

A media pipeline chains two models — an image generator followed by an upscaler — into a single fal workflow. The /workflows endpoints list and resolve workflow definitions by username and workflow name, and the queue endpoints submit requests against them. Reduces orchestration complexity for multi-step generative flows.

Call GET /workflows to find an existing workflow, then GET /workflows/{username}/{workflow_name} to resolve its definition, and submit a request through the serverless app queue with the workflow inputs.

Cost Estimation Before Submission

A finance-aware application estimates the cost of a model call before submitting it to avoid runaway spend on generative workloads. The flow uses /models/pricing/estimate with the prompt parameters and returns a price the user can approve before the request is queued. Suited to consumer-facing apps where cost guardrails matter.

POST the model id and parameters to /models/pricing/estimate, surface the returned price to the user for approval, and only then submit the inference request to the queue.

Usage and Billing Analytics

An ops engineer monitors generative spend across a workspace by reading usage, analytics, and billing events from fal. The /models/usage, /models/analytics, and /models/billing-events endpoints expose request counts, latency, and cost over time so the team can track which models are driving spend. Designed for weekly cost reviews on a generative product.

Call GET /models/usage and GET /models/billing-events for the workspace, group results by model id, and return the top spenders for the past week.

AI Agent Generative Helper

An AI agent that produces marketing assets on demand uses Jentic to discover the fal model catalogue and submit inference requests without holding the API key. Jentic exposes the 32 fal operations with their input schemas, so the agent can list models, estimate cost, and queue a request inside a single conversation. Designed for marketing or creative teams running an internal generative assistant.

Call jentic.search with 'run a fal image model', load /models to find the right model id, and submit the inference request through the serverless app queue with the user's prompt.

Key Endpoints

32 endpoints — fal is a managed inference platform for generative ai models, with a particular focus on image, video, and audio diffusion.

METHOD

PATH

DESCRIPTION

GET

/models

List available models on the platform

GET

/models/pricing

Read model pricing

POST

/models/pricing/estimate

Estimate the cost of a model call

GET

/models/usage

Read workspace usage

GET

/models/billing-events

Read billing events

GET

/workflows

List workflows

GET

/serverless/apps/{owner}/{name}/queue

Inspect the serverless app queue

GET

/models

List available models on the platform

GET

/models/pricing

Read model pricing

POST

/models/pricing/estimate

Estimate the cost of a model call

GET

/models/usage

Read workspace usage

GET

/models/billing-events

Read billing events

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

fal API keys (both standard and admin) are stored encrypted in the Jentic vault. Agents receive scoped execution permissions and the correct key is attached to the Authorization header at request time so secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'run a fal image model' or 'estimate fal cost') and Jentic returns the matching fal operations with their input schemas, so the agent can list models and submit inference without reading docs.

Time to first call

Direct integration: 1-2 days for auth, queue polling, and pricing logic. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using fal Platform APIs through Jentic.

What authentication does the fal API use?

fal uses an API key in the Authorization header. The spec defines two apiKey schemes (apiKey and adminApiKey) for end-user and workspace-admin operations. Through Jentic both keys are held in the vault and the correct one is attached at execution time.

Can I run a hosted diffusion model with the fal API?

Yes. List the available models via GET /models, optionally call POST /models/pricing/estimate for a price preview, and submit the request through the serverless app queue. fal handles GPU scheduling and returns the generated asset.

What are the rate limits for the fal API?

Numeric per-second rate limits are not declared in the spec. fal enforces concurrency limits per workspace and per model — inspect the queue endpoint for live concurrency state and read /models/usage for historical throughput.

How do I estimate cost before submitting a request through Jentic?

Run pip install jentic, call jentic.search with 'estimate fal model cost', load the /models/pricing/estimate operation, and execute it with the model id and parameters. The returned cost is delivered to the agent before the inference request is submitted.

Does the fal API support multi-model workflows?

Yes. The /workflows endpoints list workflows and GET /workflows/{username}/{workflow_name} resolves a specific workflow definition. Inference requests can target a workflow rather than a single model so multi-step pipelines run as one queue submission.

How do I track generative spend with the fal API?

Call GET /models/usage and GET /models/billing-events for workspace-level cost data. The endpoints expose request counts, latency, and billed cost per model so a spend dashboard can be built on top without further integration.