Stock, rentals & assignments

Read stock

GET /api/v1/stock returns plans and purchases_enabled. Plans contain resource targets, prices, billing terms and verified availability. Reading stock or requesting an MCP quote does not hold capacity.

Purchase

curl -X POST "$COMPUTERUSE_API_ORIGIN/api/v1/purchases" \
  -H "Authorization: Bearer $COMPUTERUSE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: stable-order-identifier" \
  -d '{"plan":"standard","term":"30_days"}'

Requires rentals:write, sufficient prepaid credit, verified stock and open checkout. Allowed plans: standard, creator. Terms: 30_days or 1_year; omitted term defaults to 30_days. This spends prepaid credit, so use it only after the buyer authorizes the purchase. Checkout currently returns 503 in the prelaunch deployment configuration.

List and inspect

Use GET /api/v1/account with account:read. The returned rentals include the rental ID, state, plan, amount, term, renewal preference and period boundaries. Treat provisioning as pending until controller readiness is confirmed.

Assign an agent

POST /api/v1/assignments accepts rental_id and agent_id. Requires agents:write and an owned active rental. It records the association; desktop control needs the separately planned session service.

Stop automatic renewal

POST /api/v1/rentals/renewal accepts rental_id and a boolean auto_renew. It is an owned-rental operation requiring rentals:write. Turning renewal off does not erase files or end the already paid term.

Order several computers together

Use POST /api/v1/orders with a rentals:write credential and an Idempotency-Key header. Mix the two plans in one order:

{
  "items": [
    {"plan": "standard", "quantity": 2},
    {"plan": "creator", "quantity": 1}
  ],
  "term": "30_days"
}

This example costs $89.97 per 30 days for three computers at the current planned prices. The limit is 100 computers per order and is also constrained by verified stock and available credit. Quantities must be positive integers. Repeated lines for the same plan are combined.

The service checks and reserves the complete fleet in one transaction. If any line lacks stock or the total exceeds credit, nothing is reserved or debited. Repeating an identical order with the same key does not debit again; changing the normalized order with that key returns 409.

Each returned rental has its own identifier, provisioning state, agent association and renewal preference. Reservation is atomic; physical provisioning happens separately for each computer. A confirmed provisioning failure refunds that computer, while an uncertain result waits for reconciliation. The existing single-computer /purchases endpoint remains supported. Checkout currently returns 503 until launch verification.