> 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-09/d.r.a.g/d-durvasa-and-ambarish-1-5.md).

# D – Durvasa and Ambarish (1-5)

*Ambarish Maharaja worshipped Lord Krishna in a multitude of ways and displayed a unique intensity of spiritual absorption. When his life was threatened by a fiery demon created by Durvasa Muni, he remained entirely undisturbed. To punish Durvasa for his harshness, Lord Vishnu released His Chakra to kill him, and the sage had to literally ‘run for his life.’ After being chased around the universe, Durvasa realised the only recourse was to beg for Ambarish’s forgiveness. The Lord cannot tolerate any offence to His devotees, who are more dear to Him than His own life. These chapters thus describe the Surya Vamsa (descendants of the sun-god, Vivasvan).*


---

# 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-09/d.r.a.g/d-durvasa-and-ambarish-1-5.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.