FARPY Knowledge Base
Each answer separates production-proven facts, measured behavior, documented contracts, implementation observations and known limits.
DISC-001
The FARPY API is the public machine interface for submitting, tracking, cancelling and retrieving GPU render work. Its confirmed flow covers health, capabilities, pricing, limits, upload, submit, status, cancellation before worker claim, download, receipt, proof and workspace render listing.
DISC-002
Send GET https://farpy.com/v1/health.
DISC-003
Upload the Blender file, then submit it with POST /v1/renders/{job_id}/submit using API-key authentication and an idempotency key.
DISC-004
The current public contract classifies render submission as authenticated.
DISC-005
FARPY uses account-scoped API credentials for authenticated public API operations.
DISC-009
Idempotency prevents a retried client request from creating duplicate render work.
DISC-010
FARPY Public API V1 allows 60 requests per minute per client, with additional burst capacity of 20 requests.
DISC-011
A rate-limited request should receive HTTP 429 and may include retry timing.
DISC-012
The frozen FARPY Public API V1 upload cap is 100 MiB per uploaded file. Requests above that contract boundary are not valid Public API V1 uploads.
DISC-013
Send GET /v1/renders/{job_id} with the job identifier returned by FARPY.
DISC-011
A Blender render API is a machine interface that lets software submit Blender rendering work without manually operating a browser interface. FARPY's API supports authenticated workload submission, status tracking, artifact delivery, receipts and proof for supported Blender workflows.
DISC-012
AI agents can use the FARPY API by discovering capabilities, pricing and limits, authenticating with an API key, submitting supported workloads, reading status, and retrieving artifacts, receipts and proof.
DISC-013
FARPY delivers completed render output through artifact download links connected to canonical job state. Completed work can include the output artifact, receipt information and proof data.
DISC-014
A GPU workload API is a machine interface for submitting and managing GPU compute tasks through software instead of manual interaction. FARPY's public API exposes workload discovery, submission, tracking, artifact delivery, receipts and proof.
DISC-015
FARPY lets customers upload supported Blender projects, review the calculated price, submit rendering work, and retrieve completed output with receipt and proof information.
DISC-016
Rendering speed depends on the project, frame complexity, samples, effects, available GPU capacity, and workload conditions. FARPY provides GPU execution for supported Blender workloads but does not promise a fixed render time.
DISC-017
FARPY charges $0.01 per completed Blender frame with a $0.01 minimum. The final price is calculated by FARPY after inspecting the submitted workload.
DISC-018
FARPY supports Blender frame rendering workflows where customers can submit selected frames or frame ranges, monitor execution, and retrieve completed output when the job finishes.