Skip to Content
Sandcovery

Routing

Pick providers by price, start latency, or uptime, and fall back when a create fails.

How a create is routed

  1. Sandcovery lists the providers you hold a credential for.
  2. It drops each provider that cannot run your spec, that your API key does not allow, or that your preferences exclude.
  3. It ranks the rest by list price and by the last 15 minutes of provider health.
  4. It creates on the first candidate and, when fallbacks are on, moves to the next one after a failed create.

A create counts as failed on a capacity or quota error, a provider 5xx, or a timeout. The response and the activity log list every attempt.

Provider preferences

Set preferences in the provider object of a create request.

FieldMeaning
orderProviders to try first, in this order
onlyThe only providers to use
ignoreProviders to skip
sortRank by price, latency, or uptime
allow_fallbacksWhether to try the next candidate after a failed create (default true)
{
  "size": "2x4",
  "provider": {
    "order": ["daytona", "e2b"],
    "allow_fallbacks": true
  }
}

Routing suffixes

A standard size name takes a suffix that sets the ranking for that create.

SuffixRanks candidates by
:cheapestList price
:fastestMeasured start latency
:most-reliableUptime over the last 15 minutes
{ "size": "2x4:cheapest" }

A size with no suffix uses default routing, which balances price, speed, and reliability and spreads concurrent load across providers.

On this page