Render from Discord
FarpyBot uses the same FARPY contract as the website: inspect, exact quote, explicit approval, ZIP, receipt. Do not paste an API key into Discord.
How it works
- Sign in. Open FARPY and sign in with the account that holds wallet credit and job history.
- Generate a one-time link code. In Account Settings → Discord, generate a one-time link code. That code is not an API key.
- DM FarpyBot. Send FarpyBot /link CODE in a Discord DM. Linking binds this Discord user to your FARPY account.
- Upload your .blend. Send the .blend in the DM. Limits match the site: Blender 4.1.1 Cycles GPU, up to 100 MiB, 1–10,000 frames.
- Choose frames. Pick the frame range you want quoted. FARPY inspects the file first. Inspect does not spend.
- Approve the exact quote. FARPY shows an exact fixed quote. Approve it to start. That is the spend boundary, same as the website.
- Receive ZIP + receipt. When the job completes, FarpyBot returns the ZIP and a receipt. SHA-256 on the receipt is byte identity of that ZIP.
Do not paste an API key into Discord
Discord linking uses a one-time code from Account Settings. API keys stay in Account Settings for REST and MCP. Pasting a farpy_agent_ or farpy_ key into Discord is the wrong path and is not how FarpyBot authenticates.
Same quote as the site
Rendering from 1¢ per completed frame. Exact price before start. When you want the browser dropzone instead: Upload your .blend for an exact fixed quote.
Other live doors: MCP for agents · Docs · Proof. IRC, Matrix, Slack, and Telegram come later.