---
title: stack es inference delete cli command
description: Delete an inference endpoint. 
url: https://www.elastic.co/elastic/docs-builder/docs/4097/reference/elastic-cli/cli/stack/es/inference/delete
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack es inference delete cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es inference delete --inference-id <inference-id> [options]
```

Delete an inference endpoint.

## Options

<definitions>
  <definition term="--inference-id string required">
    The inference identifier.
  </definition>
  <definition term="--dry-run">
    When true, checks the semantic_text fields and inference processors that reference the endpoint and returns them in a list, but does not delete the endpoint.
  </definition>
  <definition term="--force">
    When true, the inference endpoint is forcefully deleted even if it is still being used by ingest processors or semantic text fields.
  </definition>
  <definition term="--task-type enum">
    The task type
    **Values:** sparse_embedding, text_embedding, rerank, completion, chat_completion, embedding
  </definition>
  <definition term="--error-trace">
    When set to `true` Elasticsearch will include the full stack trace of errors
    when they occur.
  </definition>
  <definition term="--filter-path string">
    Comma-separated list of filters in dot notation which reduce the response
    returned by Elasticsearch.
    **Repeatable:** pass `--filter-path` multiple times to supply more than one value
  </definition>
  <definition term="--human">
    When set to `true` will return statistics in a format suitable for humans.
    For example `"exists_time": "1h"` for humans and
    `"exists_time_in_millis": 3600000` for computers. When disabled the human
    readable values will be omitted. This makes sense for responses being consumed
    only by machines.
  </definition>
  <definition term="--pretty">
    If set to `true` the returned JSON will be "pretty-formatted". Only use
    this option for debugging only.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--yes">
    confirm destructive action without prompting
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>