Get support

Open a case at AmpleRun Support while signed into the affected account. For a rental issue, include its job ID; the link https://amplerun.com/support?job=<job_id> preselects the rental context where supported.

Before opening the case

Check the current response, not just an old screenshot. The public API status at https://amplerun-api.spiry.org/api/v1/status reports minimal service identity, contract version, and whether paid admissions are paused. It is not proof that every model, payment route, or machine is working.

If an operation timed out, inspect its existing state before sending a new paid request. Keep the original idempotency key privately for recovery. Do not create duplicate rentals, deposits, or withdrawal requests as a diagnostic step.

Include these details

Issue	Useful evidence
API or MCP request	UTC time, operation/tool, HTTP status, error code, request ID, client/package version
Rental	Job ID, template and offer IDs, state, expected behavior, relevant receipt fields
Deposit	Public transaction hash if available, network, asset contract, amount, destination, reported deposit state
Host	Machine ID, operating system, selected tier/mode, installed agent version, redacted failing check
Documentation	Page URL, exact unclear or incorrect instruction, and the response or version that differs

Provide a short sequence of steps that reproduces the problem. Distinguish what the service returned from what your client inferred. For example, “reservation returned 202, then state stayed STARTING” is more useful than “rental succeeded but nothing works.”

Keep secrets out of the case

Never attach wallet private keys, API keys, enrollment credentials, pairing tokens, raw environment files, or an unredacted access response. Crop or redact terminal output before uploading it. Request IDs and public resource identifiers are usually sufficient to begin an investigation.

For SSH host-key mismatches, signature-verification failures, or unexpected money movement, stop the affected action and report the actual check result. Do not disable verification or resend funds to make the error disappear.

Documentation examples describe supported workflows, not a promise that every hardware configuration or funded on-chain path has been tested in your environment. Report the exact remaining step so it can be investigated without overstating completion.