Settings

Routing Strategy Default

The routing_strategy field in provider settings sets your per-user default. All inference requests will use this strategy unless overridden per-request. See the Routing Guide for details on each strategy.

Payout Configuration

The payout object in the GET /v1/settings response shows your current payout setup:

"payout": {
  "rail": "tempo",                         // "stripe" or "tempo"
  "tempo_wallet_address": "0xab12...cd34", // active Tempo payout address (null if none)
  "tempo_wallet_passkey": "0xab12...cd34", // permanent passkey-derived address (null if none)
  "stripe_connected": true,                // Stripe Connect onboarding complete
  "has_passkey": true                      // user has a passkey registered
}

• rail — which payout method receives future earnings.
• tempo_wallet_address — the active Tempo payout address. May be the passkey-derived address or a manually-connected wallet.
• tempo_wallet_passkey — the permanent passkey-derived address. Set once, never cleared.
• stripe_connected — whether Stripe Express onboarding is complete.
• has_passkey — whether the user has a passkey (eligible for one-click wallet derivation if tempo_wallet_passkey is null).

Payment Rail Toggles

Use PATCH /v1/settings/provider/rails to control which buyer payment rails your provider instances accept:

curl -X PATCH https://api.vram.supply/v1/settings/provider/rails \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{"accepts_stripe": true, "accepts_tempo": true}'

At least one rail must remain enabled. Both parameters are optional — omitted fields keep their current value. This applies to all provider instances under your account.