> For the complete documentation index, see [llms.txt](https://docs.developer.singpass.gov.sg/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developer.singpass.gov.sg/docs/data-catalog-myinfo/understanding-the-data/local-registered-birth-records-and-sponsored-child-records.md). # Local Registered Birth Records and Sponsored Child Records Local Registered Birth Records and Sponsored Child Records are available via Myinfo. Details available in [Myinfo data catalogue](https://docs.developer.singpass.gov.sg/singpass-developer-docs/data-catalog-myinfo/catalog). Note that the records are only based on ICA's electronic birth certificate records from 1985 onwards. If the children or sponsored children are 21 and above, only the Birth Cert Number or NRIC/FIN will be displayed. Local Registered Birth Records refer to local Singapore registered birth records. Children birth records are available in both parents' Myinfo data. Sponsored Child Records refer to children born outside Singapore. Sponsored children records are only available in the sponsoring parent's Myinfo data based on ICA's record. You can derive son, daughter or guardian relationship using children birth or sponsored children records. Spouse records are not available via Myinfo. If the marriage is registered in Singapore, Marriage Certificate Number and Marriage Date is available via Myinfo. We have observed partners retrieving both husband and wife's Marriage details to verify spouse relationship. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.developer.singpass.gov.sg/docs/data-catalog-myinfo/understanding-the-data/local-registered-birth-records-and-sponsored-child-records.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.