CLOUD GPU JOBS FOR AI AGENTS
Your AI agent sends training, evaluation and batch inference to a cloud GPU without leaving the conversation.
Symbioza manages the compute. You set the spending limit.
Free estimate with an account. Runs use prepaid credit — from $10, no subscription.
01 / THE HANDOFF
Describe the job, review an estimate, and check the files and charges when it ends.
“Run my evaluation.
Keep it under $2.”
You set the work and the limit. Your agent carries the request through Symbioza.
You provide the code and data. Your agent prepares the job and asks for an estimate.
An estimate books no compute and is not a final price. Your spending limit covers the total job charge, including retries.
File delivery and billing have separate statuses. A charge can remain provisional after a job ends.
CONNECT YOUR ASSISTANT
Run GPU jobs from the assistant you already use. Get an estimate, set your spending limit and collect the results through Symbioza.
02 / WORK TO RESULTS
Bring your container image, the command to run and where the data is. Define the output files you want to collect.
Ask your agent for a free estimate. Review it before submitting a run that spends prepaid credit.
Symbioza manages the run. Recovery follows your job policy and remaining budget.
EXAMPLE OUTPUTS + RUN RECEIPT · FILES AND CHARGES REPORTED SEPARATELY
Run your training script on cloud compute. Save model weights and logs as outputs.
“Run my training script on this dataset. Save the model and metrics. Keep the whole run under $10.”
Bring a container and training code. Checkpoint recovery requires compatible save-and-resume logic.
Run your evaluation suite and get the numbers back in a repeatable format.
“Run my evaluation harness and return metrics.json. Estimate first, with a $2 spending limit.”
Use the same model, dataset and evaluation code when comparing runs. Check the run record for execution details.
Run batch inference using a dataset URL. Collect predictions as output files.
“Score this dataset using my container. Read it from this URL and return predictions.csv.”
Declare the data and output paths. The estimate depends on the actual workload and transfer needs.
03 / YOUR FIRST ESTIMATE
Start with a free GPU job estimate. Review the expected cost and workload requirements with your agent before you add credit for a run.
Already have an account? Sign in. No prepaid credit needed to estimate.
An estimate books no compute.
Use Claude Code or a compatible MCP client. Add the connector, then follow the client’s sign-in flow.
Claude Code: install the plugin — claude plugin marketplace add symbioza/claude-plugin then claude plugin install symbioza@symbioza. Other MCP clients: add the connector URL.
MCP connects your agent to Symbioza’s tools. Your client must support remote HTTP connections and sign-in.
The Claude Code plugin, ChatGPT and other clients: Integrations →
Have your container, command, data location and output paths ready. Your agent can help prepare the request.
Copy the URL or example prompt to use in your agent.
Submitting is a separate step and uses prepaid credit. Review the job and spending limit in your client before submission.
BEFORE YOU RUN
Estimates are free. Submitted runs use your prepaid balance. Top up when you are ready. Retries stay inside the spending limit you set, never on top of it. A job that fails, or that you cancel, is billed for the resources it used — the machine time including setup, staging and the time after your command ended, storage and data transfer, and our handling of the run — never more than the spending limit you set.
No. It is an estimate for the job you describe, not a reservation or a guarantee of availability. The charge shown after completion may change while billing is reconciled. Your total charge for the job, including retries, will not exceed your spending limit.
A retry or move to another machine depends on the job policy, available compute and remaining budget. Checkpoint recovery needs compatible save-and-resume logic in your code. A run may stop without completing.
Check the file delivery status separately from the run status. Available output files have download links and hashes you can verify. A completed run does not by itself confirm file delivery or final billing.
Jobs run on third-party compute. Job records and outputs may be retained after a run. Review the Privacy notice for processing, sharing and retention, and only submit code and data you have permission to use.
The current Terms say top-ups are generally non-refundable, with unspent credit returned if the service closes and any mandatory consumer rights preserved. Read the full terms before adding credit.
