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/api/health.
DISC-003
Use POST /api/submit after obtaining the required authentication and preparing the required request fields.
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 enforces request rate limits, but the final page must publish only values confirmed by the active contract.
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 a non-mutating GET request to `/status?job_id={job_id}`, replacing `{job_id}` with the FARPY job identifier returned at submission. A successful read returns HTTP 200 JSON containing the current job state and other sanitized status fields available for that job.