FARPY Question DISC-012
What is the FARPY upload limit?
Direct answer
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.
Practical use
Check file size before upload. Keep the complete request body within the documented boundary and treat an oversized-file rejection as a request problem, not a retryable render failure.
What production evidence confirms
- **PROVEN_PRODUCTION:** The frozen Public API V1 upload cap is 100 MiB. Evidence: `upload-limit.txt`
- **PROVEN_PRODUCTION:** The frozen FARPY Public API V1 upload cap is 100 MiB. Evidence: `upload-limit-exact.txt`
- **OBSERVED:** The active upload boundary includes rejection behavior for oversized requests. Evidence: `upload-limit-exact.txt`
Failure and misuse cases
- Do not infer undocumented operations, limits or guarantees.
- Do not treat request rejection as proof that render execution failed.
- Do not expose API credentials in browser code, logs or public examples.
- Do not automate retries without checking whether the error is retryable.
Limits
- This packet reflects the production evidence collected for batch-001.
- Historical routes and old configuration files are not authoritative.
- No unsupported endpoint may be introduced during drafting.
- No oversized upload was performed during this documentation evidence pass.
- No oversized upload was intentionally transmitted during documentation validation. The 100 MiB limit comes from frozen production evidence.
Evidence boundary
This page separates frozen production facts from implementation guidance. Claims
are limited to the cited Public API V1 evidence. Missing details are not guessed.
Guidance for AI agents
Read health, capabilities, pricing and limits before performing work. Preserve
request identifiers, use idempotency where supported, obey retry timing and stop
when the contract or evidence does not support the requested action.
Related confirmed resources
- `/api/`
- `/developers/reference/`
- `/api-contract.json`
- `/questions/`
Source status
- Packet status before drafting: `ELIGIBLE_FOR_DRAFT`
- Truth review: pass
- Duplicate review: pass
- Kaizen pass 1: pass
- Kaizen pass 2: pass
- Publication: blocked pending structured data and route gates
Quality record
- Truth gate: PASS
- Kaizen pass 1: PASS
- Kaizen pass 2: PASS
- Duplicate gate: PASS