> ## Documentation Index > Fetch the complete documentation index at: https://docs.kiteml.com/llms.txt > Use this file to discover all available pages before exploring further. # Validate Sim Run > **Preview.** Usable today, but this endpoint can change before it is stable, without a new `Kite-Version`. Changes are announced before they ship. Everything a create checks, for free, without creating anything: the spec parses and resolves, the files it names are all here (`files_required` lists any that are not), every Python file is one Kite ships (`code_not_allowed`), and `kite plan`'s answer: each evaluator's status, the episodes and the estimate. A spec error keeps the SDK's diagnosis: `param` is its field (`polciy`), `details.kite_code` its code (`SPEC.UNKNOWN_FIELD`), `details.remediation` the fix and `details.location` the line (`specs/demo.yaml:5`). ## OpenAPI ````yaml /api-reference/openapi.json post /v1/sim_runs/validate openapi: 3.1.0 info: title: Kite Platform API description: >- Public API for Kite. Authenticate with `Authorization: Bearer kite_...`, and send `Kite-Version: 2026-09-27` to pin the dated contract your code was written against (without it you get 2026-09-27). Every response carries the version that served it. version: '2026-09-27' servers: - url: https://api.kiteml.com description: Kite Platform API security: - bearerAuth: [] tags: - name: Augmentations description: Generate new episodes from a LeRobot dataset. - name: Training runs description: Fine-tune a policy on a dataset, one run per policy. - name: Twins description: Rebuild a robot episode as an interactable MuJoCo scene (private beta). - name: RL runs description: >- Train a robot policy in simulation from a task spec; get the policy, its scene and a verdict. - name: Evaluations description: >- Preview. Run a policy across simulated scenarios; get its success rate, failure reasons and edge cases. - name: Scenarios description: >- Preview. The scenarios an evaluation runs, and your own, composed from robots, tasks and objects. - name: Objects and environments description: Preview. Bring your own objects and environments to your scenarios. - name: Sim runs description: >- Preview. Run a Kite SDK spec on Kite's machines: episodes, evaluators and a scorecard (enabled per account). - name: Catalog description: Policies, hardware tiers, and dataset inspection. - name: Operations description: Poll any run by its id. - name: Webhooks description: Endpoints that receive events, and the event log. - name: API keys description: The key making the request. - name: Usage description: Token usage and credit balance. - name: Requests description: >- The request log: every call of the last 30 days, who made it and how it ended. - name: Status description: Whether Kite is up, part by part. Needs no key. paths: /v1/sim_runs/validate: post: tags: - Sim runs summary: Validate Sim Run description: >- **Preview.** Usable today, but this endpoint can change before it is stable, without a new `Kite-Version`. Changes are announced before they ship. Everything a create checks, for free, without creating anything: the spec parses and resolves, the files it names are all here (`files_required` lists any that are not), every Python file is one Kite ships (`code_not_allowed`), and `kite plan`'s answer: each evaluator's status, the episodes and the estimate. A spec error keeps the SDK's diagnosis: `param` is its field (`polciy`), `details.kite_code` its code (`SPEC.UNKNOWN_FIELD`), `details.remediation` the fix and `details.location` the line (`specs/demo.yaml:5`). operationId: validate_sim_run_v1_sim_runs_validate_post parameters: - $ref: '#/components/parameters/KiteVersion' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SimRunValidate' example: files: ../evals: kind: directory shipped: evals spec_path: specs/smoke.yaml spec_yaml: |- kite_spec_version: "2" name: smoke policy: {kind: scripted_pick, ref: scripted_pick} ... responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/SimRunValidation' '400': description: >- Invalid request (`parameter_invalid`, `unsupported_version`, ...); `param` names the field content: application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' '401': description: Missing or invalid API key (`unauthenticated`) content: application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' '403': description: >- The key lacks a scope this route needs (`missing_scope`), or the feature is not enabled for the account content: application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' '429': description: >- Rate or concurrency limited (`rate_limit_exceeded`, `concurrency_limit_exceeded`, `capacity_exceeded`); honor `Retry-After` content: application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' '503': content: application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' description: >- Temporarily unavailable (`service_unavailable`); retry after `Retry-After` components: parameters: KiteVersion: name: Kite-Version in: header required: false description: >- The dated contract your code was written against. Without it you get 2026-09-27; every response says which version served it. schema: type: string enum: - '2026-09-27' default: '2026-09-27' schemas: SimRunValidate: properties: spec_yaml: type: string maxLength: 2000000 minLength: 1 title: Spec Yaml description: The spec file's text, as written spec_path: type: string maxLength: 500 title: Spec Path description: 'Its path in your workspace: what errors cite' default: spec.yaml files: additionalProperties: $ref: '#/components/schemas/SimFile' type: object title: Files description: Each path the spec names, as it names it overrides: items: type: string type: array maxItems: 100 title: Overrides description: '`FIELD=VALUE`, as `kite --set`' kite_version: anyOf: - type: string maxLength: 40 - type: 'null' title: Kite Version description: The Kite release to run; default the latest additionalProperties: false type: object required: - spec_yaml title: SimRunValidate description: >- The checks a create runs (`kite plan`), without creating anything or spending anything. examples: - files: ../evals: kind: directory shipped: evals spec_path: specs/smoke.yaml spec_yaml: |- kite_spec_version: "2" name: smoke policy: {kind: scripted_pick, ref: scripted_pick} ... SimRunValidation: properties: object: type: string enum: - sim_run_validation const: sim_run_validation title: Object default: sim_run_validation ok: type: boolean title: Ok kite_version: anyOf: - type: string - type: 'null' title: Kite Version plan: type: object title: Plan description: >- `kite plan`'s answer: the resolved spec, each evaluator's status, the episodes and the estimate price: type: object title: Price description: >- What a run of it reserves: its tier, the tier's tokens per hour, the cap in minutes and the tokens reserved (0 while billing is off) type: object required: - ok - plan - price title: SimRunValidation ApiErrorResponse: properties: error: $ref: '#/components/schemas/ApiErrorBody' type: object required: - error title: ApiErrorResponse description: Every /v1 error has this shape. SimFile: properties: kind: type: string enum: - file - directory title: Kind default: file shipped: anyOf: - type: string maxLength: 500 - type: 'null' title: Shipped description: >- A path Kite ships, e.g. `evals` or `profiles/orin-agx-64gb.estimated.yaml` sha256: anyOf: - type: string pattern: ^[0-9a-f]{64}$ - type: 'null' title: Sha256 description: >- Its hash: alone, a file or directory Kite ships; with content, a check text: anyOf: - type: string maxLength: 2000000 - type: 'null' title: Text description: A text file's content base64: anyOf: - type: string maxLength: 20000000 - type: 'null' title: Base64 description: A file's bytes, or a directory as a .tar hf: anyOf: - $ref: '#/components/schemas/SimHfFile' - type: 'null' description: A file of a public Hugging Face repository, at a commit additionalProperties: false type: object title: SimFile description: >- Where the bytes of one path the spec names come from. Exactly one of `shipped`, `text`, `base64`, `hf`, or a `sha256` the catalog lists. (Uploads by URL come with /v1/files.) ApiErrorBody: properties: type: type: string title: Type description: >- invalid_request_error, authentication_error, permission_error, not_found_error, conflict_error, rate_limit_error, or api_error code: type: string title: Code description: 'Machine-readable: branch on this, not on the message' message: type: string title: Message param: anyOf: - type: string - type: 'null' title: Param description: The request field the error is about, when there is one request_id: anyOf: - type: string - type: 'null' title: Request Id description: Also in the X-Request-Id header; quote it to support details: anyOf: - type: object - type: 'null' title: Details description: >- Extra data for some codes (e.g. the cameras a dataset does have, for camera_not_found) type: object required: - type - code - message title: ApiErrorBody SimHfFile: properties: repo: type: string pattern: ^[A-Za-z0-9][A-Za-z0-9._-]{0,95}/[A-Za-z0-9][A-Za-z0-9._-]{0,95}$ title: Repo description: '`OWNER/NAME`' revision: type: string pattern: ^[0-9a-f]{40}$ title: Revision description: 'A full commit hash: a branch or a tag moves' path: type: string maxLength: 500 minLength: 1 title: Path description: The file's path in the repository repo_type: type: string enum: - model - dataset title: Repo Type default: model additionalProperties: false type: object required: - repo - revision - path title: SimHfFile description: >- One file of a public Hugging Face repository at a commit: Kite checks it exists and pins its sha256 when the run is created, and the run's job downloads it. securitySchemes: bearerAuth: type: http scheme: bearer description: >- A Kite API key (`kite_...`), from **Platform API → Keys** in the dashboard. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.