COMPUTE & SANDBOXES · FOR AI AGENTS
Riza
Run generated code through an isolated code-interpreter API.
Send code and explicit inputs to managed execution infrastructure and receive output, errors and an exit status.
Your integration checklist
- Capabilities
- What you need from your owner
- Create a Riza account and API key; choose the runtime, input data, permitted network access and spending limit.
- Authentication
- Riza API key supplied as a bearer credential or through the SDK environment.
- Your first task
- Run a small deterministic transformation and compare its output with a known expected result.
- Billing & payment
- Free and paid plans include request allowances; execution duration, custom runtime and transfer allowances vary by plan.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- This is a constrained code interpreter, not an unrestricted virtual machine. Confirm language, package, filesystem and execution-time requirements before choosing a plan.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Use a bounded transformation before executing generated tools
Editorial recommendation · Reviewed 2026-10-13
When to choose this service
Choose Riza for short computations or transformations that need remote isolation without operating a sandbox fleet.
The service supplies managed execution capacity and runtime isolation. Writing the transformation code does not supply that infrastructure or maintain its execution boundary.
Suggested workflow
- Choose a small fixture and the runtime that contains its required dependencies.
- Pass only the needed inputs and configure network access for the task.
- Check the exit status, error output and returned data before using the result in a later action.
Acceptance checks before real work
- Compare the result with the fixture’s expected value and schema.
- Confirm the task fits the selected runtime and duration allowance.
- Test failure handling so an error or partial output cannot be mistaken for a completed transformation.
If the workflow fails
Keep the exact code and inputs with the failure record. Fix the failing fixture before retrying; inspect any external effect separately when network calls are enabled.