Prepare appropriate request body based on your input and desired outcome.
apiKey in query parameters and declaredJobSize in the request body.
Job size determines what machine will be used to run trace generation. It also affects the cost of the query. You should choose job size based on number of steps you expect the program execution to have.
| Number of steps [millions] | Size | Cost |
|---|---|---|
| 0 - 13 | S | 70 |
| 13 - 30 | M | 120 |
| >30 | L | 220 |
programFile.json)pie.zip file)
programFileinputFile (optional) - available only for Cairo1 and Cairo0 with Rust VMlayout (can be set to auto)cairoVersionresult = TRACE_GENERATIONpieFile must be left emptypie.zip)proof.json)
programFileinputFile (optional) - available only for Cairo1 and Cairo0 with Rust VMlayout (can be set to auto)cairoVersionresult = PROOF_GENERATIONpieFile must be left emptyproof.json)programFileinputFile (optional) - available only for Cairo1 and Cairo0 with Rust VMlayout (can be set to auto)cairoVersionresult = PROOF_VERIFICATION_ON_L1pieFile must be left emptyprogramFileinputFile (optional) - available only for Cairo1 and Cairo0 with Rust VMlayout (can be set to auto)cairoVersionresult = PROOF_VERIFICATION_ON_L2pieFile must be left emptypie.zip)proof.json)
pieFilelayout (can be set to auto)result = PROOF_GENERATIONproof.json)pieFilelayout (can be set to auto)result = PROOF_VERIFICATION_ON_L1pieFilelayout (can be set to auto)result = PROOF_VERIFICATION_ON_L2