> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-apis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-apis/accessing-os-apis/os-ngd-api-tiles/technical-specification.md). # Technical specification OS NGD API – Tiles technical specification provides an overview of the endpoints available, as well as the parameters that can be used with each endpoint. The Technical Specification is intended to be used by customers who want to integrate with the API.\ \ The service offers the following endpoints:


Landing page	OS NGD API – Tiles landing page.	Landing page
Conformance	List the OS NGD API – Tiles conformance to the OGC API - Tiles specification.	Conformance
Collections	Get a list of all the available tile layers available.	Collections
Collection	Get information about a specific tile layer.	Collection
Tile Matrix Sets	Get the available tiling schemes and definition.	Tile matrix sets
Tiles	Get tilesets and vector tiles from a specific tile layer.	Tiles
Styles	Get a list of the available styles and the stylesheet.	Styles

--- # 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.os.uk/os-apis/accessing-os-apis/os-ngd-api-tiles/technical-specification.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.