> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-inventory/concepts/environment-type.md).

# Environment Type

The Environment Type feature in Akto allows users to tag API collections as either Staging or Production. This helps teams prioritize testing and triage alerts based on the environment’s criticality. Learn [How to Set Environment Type](/api-inventory/how-to/set-tags.md).

### Helps with:

1. **Tagging API Collections:** Label collections as Staging or Production for better management.
2. **Environment-Specific Testing:** Adjust testing efforts based on the environment, avoiding unnecessary tests in Production while prioritizing urgent issues there.
3. **Efficient Triaging:** Alerts for sensitive data or vulnerabilities in Production are prioritized over Staging, ensuring quick action where it’s most needed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akto.io/api-inventory/concepts/environment-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.