Render Farm API for automation

Canonical machine contract

Public API V1 uses https://farpy.com/v1. Render requests authenticate with Authorization: Bearer and a FARPY API key.

• Capabilities
• Pricing
• Limits
• OpenAPI 3.1.0

Farm operations exposed through the API

A traditional render farm hides machines behind submission and queue systems. FARPY exposes that operational boundary directly through Public API V1.

The caller can inspect current availability and limits before upload, calculate the canonical price, create a render record, submit it for execution, and observe state transitions.

The API does not expose private node identities or topology. Scheduling, worker claim, execution, billing, reconciliation, and artifact delivery remain server-side responsibilities.

Queue and cancellation behavior

Created work is not equivalent to claimed work. The explicit submit step separates upload from execution and supports deliberate application workflows.

Cancellation is available before worker claim. Once execution has crossed the claim boundary, the public cancellation contract no longer promises interruption.

Terminal states are completed, failed, and cancelled. Polling and signed terminal webhooks provide two supported ways to observe the final outcome.

Durable webhook delivery retries terminal notifications with bounded exponential backoff. Failed delivery records are retained rather than silently discarded.

Economic and capacity boundaries

The canonical public price is $0.01 per completed Blender Cycles frame.

Frame requests can cover 1 to 10,000 frames. Uploads are limited to 100 MiB, and request traffic is limited to 60 requests per minute plus burst capacity.

Preflight exists so automation can validate request metadata and calculate price before transferring the render payload.

Billing is tied to completed work under the public contract. Failed and cancelled terminal states are represented separately from completed delivery.

Farm output and accountability

After completion, the caller can retrieve artifact download information, a receipt, and a proof record using the canonical job identifier.

Workspace render listing provides an authenticated account-level view of submitted jobs without exposing other customers' work.

FARPY evidence covers its qualified runtime and workload classes. It does not claim that every Blender file, add-on, external asset arrangement, or renderer configuration will execute successfully.

Implementation paths

Use the API quickstart for the granular request flow, the agent rendering guidefor low-decision automation, and thedeveloper reference for the complete endpoint contract.

Structured error handling is documented in theerror recovery guide. Signed terminal delivery is documented in the webhook guide.

Render farm operating summary

FARPY separates remote submission from execution so automation can validate, price, upload, and create work before committing it to the render queue. Worker selection, claim, GPU execution, reconciliation, billing, and artifact delivery remain server-side operations.

The public farm contract charges $0.01 per completed Blender Cycles frame. Requests support frames 1 to 10,000, a maximum upload size of 100 MiB, and 60 requests per minute plus burst capacity. Callers should inspect capabilities, pricing, limits, and OpenAPI before assuming current capacity or behavior.

Cancellation is supported before worker claim. Terminal outcomes are completed, failed, and cancelled. A completed job exposes download, receipt, and proof records. Signed terminal webhooks and canonical status polling allow software to reconcile delivery without exposing private worker identities or internal node topology. This keeps automation predictable.

Frequently asked questions

Can FARPY be used as a remote render farm?

Yes. Public API V1 exposes remote Blender Cycles submission, status, cancellation, delivery, receipt, and proof operations.

When can a queued render be cancelled?

Cancellation is available before worker claim.

How does the farm report completion?

Callers can poll canonical job status or consume signed render.completed, render.failed, and render.cancelled events.

What are the public capacity limits?

Uploads are limited to 100 MiB, frame requests support 1 to 10,000 frames, and the request limit is 60 per minute plus burst capacity.

Does the public API reveal worker topology?

No. Private node identities and topology are not exposed through the public farm interface.