> ## Documentation Index > Fetch the complete documentation index at: https://docs-stg.outerlayer.ai/llms.txt > Use this file to discover all available pages before exploring further. # Keep one of the factory's managed sandboxes, paused, after its build ends > Keeps the sandbox, paused, so that it outlives its claim. The caller must hold the live claim the sandbox was made for. The gateway marks the sandbox kept, changes its secret at the provider, and pauses it, in that order. No answer gives out the new secret, and no secret that left the gateway opens the sandbox. The answer is the sandbox with an empty `secret` and `urlToken`. A repeat of the call for a sandbox that is kept and paused makes no call to the provider, and answers with an empty `dataPlaneUrl`. A kept sandbox is not billed after its claim is released. It ends after 24 hours, when a newer kept sandbox of the same work item replaces it, or when the factory holds more than 10. A pause that gets no answer in 30 seconds does not fail the call. The every-minute check ends a kept sandbox that still runs 5 minutes after the keep. Refusals: `claim_expired` (410, the claim is released or expired, or the caller holds a newer one), `claim_not_held` (403), `sandbox_not_found` (404), `managed_sandboxes_off` (403), `managed_sandboxes_unavailable` (403) and `sandbox_provider_refused` (502). A refused secret change leaves the sandbox running and not kept. A refused pause ends the sandbox. The response is sent with `Cache-Control: no-store`. ## OpenAPI ````yaml /openapi.yaml post /v1/managed-sandboxes/{sandboxId}/keep openapi: 3.0.3 info: contact: email: hello@outerlayer.ai url: https://www.outerlayer.ai description: >- The OuterLayer Gateway API lets you ingest coding-agent sessions and record evidence of work programmatically. Most teams reach it through the `outerlayer` CLI, which calls it for them. Call it directly to build your own integration or to automate what the dashboard does. Versioning: every endpoint is prefixed with `/v1/`. Breaking changes ship under a new version prefix (`/v2/`, etc.) with a 90-day-minimum deprecation window; anything additive lands on the current prefix. Vocabulary: the dashboard calls this API's `app` a **factory** — the unit that owns a set of repositories, the agent sessions worked on them, and the evidence they produce. They are the same entity. The API keeps `app` in its paths, headers, and field names because those are a published contract; only the product surface was renamed. title: OuterLayer Gateway API version: '1.0' servers: - description: Production (OuterLayer Cloud) url: https://api.outerlayer.ai - description: Local dev server (self-hosted gateway) url: http://localhost:9418 security: - AppId: [] BearerAuth: [] tags: - description: >- What a CLI login token can read about its owner without naming a factory, such as the factories they can use. name: Account - description: >- The route a fleet machine asks for its next managed build on. A fleet machine is a machine OuterLayer operates. name: Fleet - description: >- The CLI version a gateway names to its runners, set with the gateway's runner version key. name: Runner version - description: >- Coding-agent session ingest (outerlayer sync) and content-addressed session images. name: Agents - description: >- Evidence artifacts (screenshots, recordings, reports, logs) emitted as proof of a change and anchored to pull requests. name: Artifacts - description: >- Pass/fail outcomes of checks run in your own CI or compute, anchored to pull requests with the run URL as proof. name: Emitted Results - description: >- The acceptance criteria of a work item, recorded as one list. The Criteria tab, its count and the item status read that list. name: Criteria - description: >- What any agent found wrong about a change under review or about a rule it ran on, recorded on a work item. name: Findings - description: >- Find, file and edit the issue a spec lives in, through OuterLayer, with no tracker credential on the caller's side. name: Specs - description: >- Add or remove a source's statement that it is working on an issue or pull request, and read what is currently live. name: Work Items - description: >- What the factory's GitHub App installation lets builds do on each connected repository, and whether each default branch requires a pull request. name: Repositories - description: >- The runs of a schedule automation: a runner claims a run, asks for its read token and ends it, and the run's agent reports each issue it found or that it found nothing. name: Schedule runs - description: >- A runner host's heartbeat — its CLI version, slots and last request for work — and the factory's list of hosts with a derived status. name: Hosts - description: Query server feature availability. name: Capabilities - description: Per-model LLM pricing data. Public, unauthenticated. name: Pricing - description: >- Create, list, and revoke factory API keys. Plaintext returned exactly once at creation. name: API Keys - description: >- Factory CRUD — a factory is owned by an organization and is the unit every other resource hangs off. Lets a headless agent provision one without the dashboard. name: Apps - description: >- Agent-coding session list and full transcript reads, with actor-privacy controls for machine keys. name: Sessions - description: >- Per-model token spend and fleet-wide agent behavior tiles, including two-window comparisons. name: Metrics - description: Synced-commit history of the app's `.outerlayer/` context tree. name: Context - description: >- Session→PR attribution: which agent sessions produced which pull requests, and what each attributed PR cost. name: PRs - description: Service health checks. name: Health - description: >- Org member and role administration, authenticated with an org-scoped management API key (`olk_…`) minted in the dashboard's settings. name: Org Management - description: OAuth 2.1 discovery metadata for MCP connector clients. name: OAuth paths: /v1/managed-sandboxes/{sandboxId}/keep: post: tags: - Work Items summary: >- Keep one of the factory's managed sandboxes, paused, after its build ends description: >- Keeps the sandbox, paused, so that it outlives its claim. The caller must hold the live claim the sandbox was made for. The gateway marks the sandbox kept, changes its secret at the provider, and pauses it, in that order. No answer gives out the new secret, and no secret that left the gateway opens the sandbox. The answer is the sandbox with an empty `secret` and `urlToken`. A repeat of the call for a sandbox that is kept and paused makes no call to the provider, and answers with an empty `dataPlaneUrl`. A kept sandbox is not billed after its claim is released. It ends after 24 hours, when a newer kept sandbox of the same work item replaces it, or when the factory holds more than 10. A pause that gets no answer in 30 seconds does not fail the call. The every-minute check ends a kept sandbox that still runs 5 minutes after the keep. Refusals: `claim_expired` (410, the claim is released or expired, or the caller holds a newer one), `claim_not_held` (403), `sandbox_not_found` (404), `managed_sandboxes_off` (403), `managed_sandboxes_unavailable` (403) and `sandbox_provider_refused` (502). A refused secret change leaves the sandbox running and not kept. A refused pause ends the sandbox. The response is sent with `Cache-Control: no-store`. operationId: keep-managed-sandbox parameters: - in: path name: sandboxId required: true schema: type: string - description: >- HTTP Message Signature (RFC 9421) made with the runner key's host key: `runner=::`. in: header name: Signature required: false schema: description: >- HTTP Message Signature (RFC 9421) made with the runner key's host key: `runner=::`. type: string - description: >- The signature's covered components and parameters: `runner=("@method" "@path" "@query" "content-digest");created=;nonce="";keyid="";alg="ed25519"`. in: header name: Signature-Input required: false schema: description: >- The signature's covered components and parameters: `runner=("@method" "@path" "@query" "content-digest");created=;nonce="";keyid="";alg="ed25519"`. type: string - description: >- RFC 9530 digest of the request body, always sent, including for a request with none: `sha-256=::`. in: header name: Content-Digest required: false schema: description: >- RFC 9530 digest of the request body, always sent, including for a request with none: `sha-256=::`. type: string responses: '200': content: application/json: schema: properties: data: properties: dataPlaneUrl: description: The address the runner sends commands and files to. type: string id: description: The provider's id of the sandbox. type: string machine: description: >- The machine size the sandbox was made with, which its build is billed at. enum: - small - large type: string metadata: additionalProperties: type: string type: object name: type: string secret: description: >- The sandbox's own secret. Hold it in memory only. Empty in a list, while the state is `starting`, for a kept sandbox, and when the claim of the sandbox is not live and billed. type: string state: description: >- `starting`, `running`, `paused` or `ended`. A sandbox that is `starting` has no usable address and no secret yet, and its build is not billed until it has started. type: string tokenHeader: description: >- The name of the header that carries `secret` on a call to `dataPlaneUrl`. type: string urlToken: description: >- The token a port address carries. Empty in a list, while the state is `starting`, for a kept sandbox, and when the claim of the sandbox is not live and billed. type: string required: - id - name - state - dataPlaneUrl - secret - urlToken - tokenHeader - machine - metadata type: object required: - data type: object description: The sandbox, kept and paused, with no secret. '400': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Invalid request parameters (validation failed). '401': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: >- Missing or invalid API key, or a runner key's signature was refused: `runner_key_signature_required` (the request carries no signature), `runner_key_signature_invalid` (it does not verify against the host key the key is bound to, or the body does not match its digest), `runner_key_signature_stale` (`created` is more than five minutes from the gateway's clock) or `runner_key_signature_replayed` (the nonce was accepted in the last five minutes). '403': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: >- Another key holds the claim (`claim_not_held`), managed sandboxes are off for the organization (`managed_sandboxes_off`), the gateway provides none (`managed_sandboxes_unavailable`), or the caller is not a runner key (`forbidden`). '404': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: The factory has no such sandbox (`sandbox_not_found`). '410': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: >- The claim of the sandbox is released, expired, or replaced by a newer one (`claim_expired`). '502': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: >- The sandbox provider refused the call or did not answer (`sandbox_provider_refused`). The body carries `providerCode` and `providerStatus`. components: securitySchemes: AppId: description: Factory id the request is scoped to. in: header name: X-Outerlayer-App-Id type: apiKey BearerAuth: description: API key (sk_outerlayer_*) scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.