Data & AI · wired today
fal.ai, wired into your agent workforce
Models and datasets are infrastructure now, and agents need eyes on them. The fal.ai connector is one of 222 executable connectors and gives agents 3 tools, with the credential held in the vault and every call receipted.
Connecting fal.ai takes one credential
You provide API key from your fal.ai account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: fal.ai's own API documentation ↗ covers creating and scoping the credential.
What agents can run against fal.ai
get_statusPoll a submitted fal.ai job for its current queue status: queued, in progress, completed or failed, plus its queue position and the result URL once done. This is the ASYNC POLL half of the submit-then-poll pattern: submit_generation (write:true) starts a job and returns a request_id, this tool is the zero-spend authed read that checks on it. Also the spec's auth-proving test call
get_resultFetch the finished output of a completed fal.ai job: the generated images, video, audio or model-specific output. Reads an existing job only; it never starts a generation
submit_generationSubmit a new generation job to a fal.ai model's async queue (image, video, audio, etc). This is the ASYNC SUBMIT half of the submit-then-poll pattern: it is a billable generation, so it is HITL-gated and never fired by the shape-proof harness. Poll the returned request_id with get_status once approved and started, then read the finished output with get_result
How proven is this?
This connector was blind shape-proven against the real fal.ai API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
- Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
- Approvable Its write tools execute only after a human approves them in the inbox.
- Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
- Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
- Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.
fal.ai integration FAQ
What can Quox agents do with fal.ai?
Agents can run 3 tools against fal.ai: get status, get result, submit generation. Every call is receipted in the evidence trail.
What does the fal.ai integration need?
You provide API key from your fal.ai account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my fal.ai credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the fal.ai connector?
This connector was blind shape-proven against the real fal.ai API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.