> 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-10-part-2/m.a.d/a-astonishing-rule-52-70/history-of-pradyumna.md). # History of Pradyumna After being burned to death by Rudra’s anger, Kamadeva was reborn as Pradyumna, the son of Krishna and Rukmini. In the maternity room, however, he was kidnapped by the demon Sambara and thrown into the ocean. A fish unexpectedly swallowed Pradyumna, and later that fish was caught and given to Sambara’s cooks. Astonishingly, they found a child in the belly, and gave him to Mayavati. Kamadeva’s previous wife, Rati, was reborn as Mayavati, and was a cook for Sambara. She was actually waiting for her husband to appear in his new body. Later, she requested Pradyumna to marry her, and advised him to also kill Sambara. Pradyumna did both, and together with his wife went to Dwaraka, where all the inhabitants were enchanted by his beauty. Rukmini was especially overjoyed to be reunited with her son. --- # 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-10-part-2/m.a.d/a-astonishing-rule-52-70/history-of-pradyumna.md?ask=&goal= ``` `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.