Replicate Deployments vs Vast.ai

Replicate Deployments

OpenAPI file, llms.txt and an MCP server with a two-tool code mode. Private instances bill set-up and idle time, H100 at $5.49 an hour.

Vast.ai

API keys can be limited by permission category and by resource ID, the REST API has a public OpenAPI 3.1 file, and the CLI ships weekly with a skill file for coding agents. Machines belong to independent hosts, prices move with the market, rate-limit thresholds are unpublished, and there is no SLA or free tier.

Replicate Deployments

1. List GET /v1/hardware first and use the returned sku in the deployment body
2. Set min_instances to 0 for bursty work; a warm H100 bills $5.49 an hour whether called or not
3. Send Prefer: wait on deployment predictions to block instead of polling
4. Copy outputs within an hour; API prediction data is deleted after that
5. Wait for the reset time in the 429 body before retrying; prediction creates cap at 600 a minute

Vast.ai

1. Create a scoped key with vastai create api-key --permissions for the agent. A default key has full account access, billing and key management included
2. Pass --raw on every CLI command for JSON output, and -y on vastai destroy instance, which otherwise waits for a confirmation prompt
3. Register an SSH key with vastai create ssh-key before creating an instance, or the host is unreachable
4. Destroy instances when finished. A stopped instance still bills storage, and a zero balance without a saved card leads to deletion
5. Back off on HTTP 429 yourself when calling REST directly. The CLI retries 429 three times from 0.15 seconds
6. Filter searches with verified=true or the Secure Cloud option for sensitive data, and set a dph_total price cap