Execution support and next steps
Distinguish catalog discovery, input preparation, plan creation, and submission, then choose the next step from the current response.
A tool listing does not establish that it can run now. Select a project and call list_execution_options to check support for your current account. Releases are published per organization, so projects in the same organization see the same results.
Which steps are available?
options— Releases available for plans through the current calling method. Keep bothreleaseIdandmanifestHash. Being listed does not authorize submission.preparationOnly— Tools with input-preparation paths. Read each entry'sworkflowSupportrather than assuming all later steps are blocked from the list name.workflowSupport.inputPreparation— Whether input preparation is supported.workflowSupport.planCreation— Whether the project has a release usable for creating a prepared plan.workflowSupport.jobSubmission— Submission support for the current calling method.plan-review-requiredrequires review of the exact plan; it is not submission permission.
reason is a machine-readable identifier; reasonText explains it. Do not invent missing reasons. The latest plan review rechecks inputs, permissions, release, approval, and other submission conditions.
Will the job start now or wait?
executionCapacity describes the servers currently able to receive this organization's GPU jobs. It is separate from submission eligibility: jobs can be accepted into the queue even when servers are absent or full.
state—available(capacity available),busy(all busy; starts when capacity frees up),none(no server connected in the last 2 minutes), orunknown(servers exist but have not reported remaining capacity).cleanDevicesis the number of GPUs with no jobs attached.maxFreeMbis the largest shareable free memory on one device, in MiB. Larger jobs wait for capacity.platformServersandorganizationServerscount servers operated by Nadoo Bio and servers connected by the organization, respectively.
Relay the response's server guidance unchanged. It contains no estimated wait time, so do not invent one.
No runtime is available yet
runtime_consumer_unavailable means the platform currently has no runtime for this tool. Additional API-key scopes or human approval cannot supply one.
Proceed only through the supported input-preparation or plan-creation steps. After creating a plan, check submissionAvailable in get_plan. Each tool's fixableBy and fixableByText identify who can resolve the restriction: platform requires Nadoo Bio to deploy a runtime; organization-operator requires an organization operator to publish a release.
No release is available for a plan
release_unavailable means there is no valid published release for creating a plan in the current project. This reason alone does not distinguish licensing, account permissions, or an unpublished release.
If input preparation is supported, complete that step and query execution options again for a release. Use the release ID returned by that response unchanged.
A new plan must be created on the web
For session_submission_required, a plan created with the current API-key method cannot be submitted even after approval. Open View execution plan from the response, then prepare and review a new plan on the web in the same project.
The existing API-key plan does not become a web plan. Keep the original plan and input records. Even a new web plan may be restricted by its inputs, permissions, and execution conditions.
The exact plan needs review first
For plan_review_required, use the returned release to create and review a plan with fixed inputs. Submission depends on its current review outcome. Successful preparation, human approval, job acceptance, and completed execution are different states.
Run Boltz with a Nadoo Bio API key
The key here is issued by Nadoo Bio, not a separate Boltz service. The agent creates a plan; the user reviews and approves its terms on the web. The agent then calls submit_plan with the same planId and planHash. Submission rechecks key permissions, approval expiry, operational settings, and usage.
If a Boltz batch returns approval.status as pending, a person must review and approve the plans and terms at the returned approval link. reviewMode: exact_plan_list approves only the selected plans, up to 100 at a time. Approval is separate from submission; after a submission request, call submit_batch with the original batchId. Older servers returning individual_plan_approval_required require individual review links from get_plan and submission through submit_plan.
After human approval, use get_plan to check current approval and usageTerms. If terms exist, check for acceptedAt and pass the returned usageTerms.termsHash unchanged as submit_batch.acceptedTermsHash. Passing a hash does not replace consent. If plans have different terms hashes, check each plan's current terms and use submit_plan individually rather than applying one hash to the batch. Retries after response loss must retain the original body and request ID.
Empty lists and permission errors
An empty list alone does not prove missing permissions. Explain a permission requirement only when an actual error such as scope_required is returned. Do not assume most tools are unavailable or that changing accounts will resolve the issue.
Tell the user which steps are supported, the returned reason, and what can be done next. See Reading input validation results for sequence errors and normalization.