CoreWeave vs Northflank

CoreWeave

Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.

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.

CoreWeave

1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as Authorization: Bearer to https://api.coreweave.com
2. Add GPUs by applying a NodePool resource (compute.coreweave.com/v1alpha1) to a CKS cluster with instanceType and targetNodes. instanceType can't be changed afterwards
3. Set targetNodes to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour
4. Never pass dry_run to the MCP tool coreweave_kubectl_apply expecting a preview. The reference says the parameter is ignored and the manifest is applied
5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there

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