Runpod vs Verda

Runpod

Per-second billing across more than a dozen serverless GPU classes, H100 at $4.79 and A100 80 GB at $2.72 an hour. Data-centre outages of 6 to 24 hours in each of July, August and September 2026.

Verda

The REST API has a public OpenAPI 3.1 document, a dated changelog, published rate limits with Retry-After, and an audit log endpoint. The CLI's MCP server refuses billed or destructive calls without confirm: true. Access needs a browser signup and a prepaid balance, credentials carry one scope, and instance creation has no idempotency key.

Runpod

1. Create a Restricted or Read Only key per endpoint for the agent, not an All key
2. Use REST v2 at api.runpod.io/v2 with a Bearer header; avoid GraphQL, which puts the key in the URL
3. Fetch /run results within 30 minutes and /runsync results within 1 minute, or they're gone
4. Call /retry on a failed job ID rather than submitting a duplicate job
5. Check /health before relying on an endpoint idle for a week, since max workers drop to 0

Verda

1. Exchange the client ID and secret at POST /v1/oauth2/token, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.
2. Send location_code on every create call. Requests without it have returned 400 since March 2026.
3. Call GET /v1/instance-availability before launching. POST /v1/instances returns 503 service_unavailable when the location has no capacity.
4. List instances before retrying a failed launch, because create has no idempotency key.
5. Use the delete action to stop charges. shutdown keeps billing, and deleted volumes stay recoverable for 96 hours unless delete_permanently is set.