Northflank vs Vast.ai

Northflank

OpenAPI 3.0 with over 100 paths, enums and per_page, page and cursor on every list. No scale to zero for services; minimum instances must be at least 1.

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.

Northflank

1. Issue the agent a team token under an API role limited to one project, not a personal token
2. Read x-ratelimit-remaining and wait x-ratelimit-reset seconds on a 429; the default is 1,000 calls an hour
3. Page lists with per_page up to 100 and the returned cursor instead of numbered pages
4. Use a job, not a service, for anything that finishes; services bill until paused or deleted
5. Fetch any docs page with .md appended to get Markdown

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