> For the complete documentation index, see [llms.txt](https://akshit-me.gitbook.io/e-courts-india-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://akshit-me.gitbook.io/e-courts-india-api/phoenix.md).

# Phoenix

Postman Collection: <https://phoenix.akshit.me>

The Phoenix database was created to help relieve the API from unnecessary stress and promote better ID management.

The Phoenix database contains the following data:

1. District Courts
   1. States - All states in India.
   2. Districts - All complexes sorted state wise.
   3. Complexes - All complexes (Collection of multiple Judges) sorted district and state wise.
   4. Courts - All courts (Judges) sorted complex, district, and state wise.
2. High Court
   1. Courts - The High courts of all the states.
   2. Benches - The benches present in the court.

What Phoenix does different than the previous approach is, it makes fetching data in an orderly manner much easier. You can now simply get data in any way you want.


---

# 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://akshit-me.gitbook.io/e-courts-india-api/phoenix.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.