factorial-compute
One API for AI compute that returns typed answers — text, images, masks, detections, depth, documents, transcripts, speech, video, 3D models, tracks — in the same shape whichever model or supplier produced it.
pip install factorial-compute
factorial login inv_... # once: saves your key for every script and agent here
from factorial_compute import Client
f = Client() # the key `factorial login` saved, or FACTORIAL_API_KEY if set
# Text, and JSON on request.
print(f.run(model="gpt-oss-120b", input="Name three uses for a forklift.").text)
# An image from a prompt.
result = f.run(model="flux-schnell", input={"prompt": "a red forklift in a warehouse"})
result.images[0].save("forklift.jpg")
# Masks: one per object, each with a box measured from the mask.
result = f.run(model="sam2-segment", input={
"image": "warehouse.jpg", # a local path: uploaded for you
"objects": [{"id": "pallet", "box": [40, 60, 300, 280]},
{"id": "cone", "point": [512, 240]}],
})
for mask in result.masks:
print(mask.id, mask.box)
mask.save(f"{mask.id}.png")
# A transcript, with timestamps.
result = f.run(model="whisper", input={"audio": "meeting.mp3"})
print(result.transcript.text)
for segment in result.transcript.segments:
print(f"{segment.start:6.1f}s {segment.text}")
That is the whole surface for most work: run() with a model id and an
input, then read the typed answer.
Rules worth knowing
- Files go in by path, URL or bytes under the keys
image,images,audioandvideo- for vision chat models too. The client uploads them and sends a reference. - Answers are typed.
.text,.images,.masks,.detections,.depth,.document,.transcript,.audio,.video,.mesh,.tracks. Asking a result for the wrong kind raises, rather than returning something empty. - Boxes are
[x0, y0, x1, y1]in pixels everywhere, so a box from a vision model or a detector can be sent straight to a segmenter. - Files come back as handles.
.save(path)writes one;.read()returns the bytes. They stay on the server until you ask. - Retries are safe. Every
run()carries an idempotency key and is retried on connection failures and on 429/502/503/504, so a retry never runs — or bills — the work twice. - Errors say what to change. A refused input raises
InvalidInputwhose message names the field and a value that works. - Reasoning models think before they answer, and the thinking counts
against
max_tokens. Too low a cap is spent thinking:.textthen raisesIncompleteAnswerrather than returning"". Give reasoning models a few thousand tokens, or sendreasoning_effort="low"to think less. - Every result says what it cost:
result.cost.usd, alongsideresult.timing.duration_ms.f.quote(model=..., input=...)says it before anything runs;max_cost_usd=onrun()orsubmit()refuses a call that would cost more, raisingCostCapExceeded. - Answers chain. Pass an earlier answer's file as an input -
{"image": result.images[0]}- and it goes by reference, never downloaded and uploaded again. - Submitted work can call back:
submit(..., webhook_url=...)posts the id and status when it finishes; fetch the execution for the answer. - Masks and boxes draw onto the photo:
result.masks.draw(photo, "out.png")tints and numbers every mask,mask.layer(photo, colour)gives one see-through layer for stacking in HTML,result.detections.draw(...)boxes. - Usage is in the model's own unit: tokens,
images,audio_seconds,characters,video_seconds_generated,object_seconds,meshes.result.usage.unitshas it.
Which models exist
for model in f.models.catalog():
print(model["id"], model.get("output"), model["unit"])
print(" ", model["example"])
The catalogue lists the models you can call right now (catalog(all=True) for
everything, with availability saying which are offline). Each entry says what
kind of answer it returns (output), what every input field means (input),
and gives an example input that works as written.
Longer work
handle = f.submit(model="flux-schnell", input={"prompt": "..."})
result = handle.wait()
submit returns before the work runs and survives your process exiting.
Metadata
Release files for factorial-compute 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| factorial_compute-0.0.6.tar.gz | 31.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| factorial_compute-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.3 kB
Release files / factorial_compute-0.0.6.tar.gz
| Download URL | factorial_compute-0.0.6.tar.gz |
|---|---|
| Size | 31.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69d985bed5d0bb3200d1ed9b8ee6581ad092355bab5f34f0728e5abf2c5e6123
|
|
BLAKE2b-256 checksum How to use checksums |
a27864fea6d0c540ea7a8300dd2665acf9b210b2fb2373cd908b396bbf130b26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / factorial_compute-0.0.6-py3-none-any.whl
| Download URL | factorial_compute-0.0.6-py3-none-any.whl |
|---|---|
| Size | 33.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1e5bea0a58f544f5ec1670302a4f19f20afbd9be0dfe62b8c5dd839d11b10e7
|
|
BLAKE2b-256 checksum How to use checksums |
bfae18f5d5354b7ee3b1a479a03c3ed28317a4f72822f9768fd9bd2011b732bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log