Scripts and CIΒΆ

Use the central HTTPS REST API with a scoped Gradient Dynamics key supplied through your secret manager or environment. Start from the REST quickstart. The Python client is an optional convenience wrapper, not a prerequisite.

For each workflow, discover capabilities, validate requests and retain job/operation/artifact identities. Use one idempotency key per intended submission and reuse it only to reconcile the same request. Poll at the returned interval, follow pagination, and keep local timeouts separate from explicit cancellation.

CI should validate request shapes and documentation without starting paid engineering jobs. If a pipeline is authorized to run compute, make its budgets, retry bounds and output acceptance criteria explicit. A refusal or failed solve is not permission to start a changed run automatically.

Use capability URLs with only their specified transfer headers. Do not forward the account bearer credential to an unrelated upload/download host. Keep private viewer links and secrets out of public logs.

See errors and recovery and agent workflow.