> For the complete documentation index, see [llms.txt](https://bhagavata.keshavaswami.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bhagavata.keshavaswami.com/canto-05/r.e.a.p/p-planetary-systems-20-26/lord-anantadeva.md).

# Lord Anantadeva

Lord Ananta, whose body is completely spiritual, resides at the root of the planet Patala. He remains in the core of Lord Siva’s heart, helping him to destroy the universes as required. He is the original deity of material consciousness, and because He attracts all living entities, He is also known as Sankarsana. The entire material world rests upon His hoods.&#x20;

Because Lord Sankarsana is an expansion of the Supreme Personality of Godhead, many devotees offer Him prayers, and in the planetary system of Patala, all the *suras*, *asuras*, Gandharvas, Vidyadharas and learned sages offer Him their respectful obeisances.


---

# 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://bhagavata.keshavaswami.com/canto-05/r.e.a.p/p-planetary-systems-20-26/lord-anantadeva.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.
