> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/index/service-overview.md).

# Service Overview

![A diagram showing the major services in wellcomecollection.org](https://raw.githubusercontent.com/wellcomecollection/.github/main/profile/services.png)

**Services**

* [wellcomecollection.org:](broken://spaces/mNeKBZYcfnVQtLDYvJ5T) The Wellcome Collection website is the public face of our digital offering, and it pulls in content from a variety of services.
* [Catalogue API: ](https://docs.wellcomecollection.org/catalogue-api/)Powers our unified collections search.&#x20;
* [Catalogue Pipeline: ](https://docs.wellcomecollection.org/catalogue-pipeline/)A data a pipeline that combines data from different library and archive catalogues.
* [Storage Service: ](https://docs.wellcomecollection.org/storage-service/)Our storage service is the long-term preservation repository for our digital collections. It keeps our files in cloud storage providers, stores multiple copies for redundancy, and verifies every copy is stored correctly.
* [Prismic](broken://spaces/451yLOIRTl5YiAJ88yIL): Our editorial content including stories, exhibitions, and events is stored and managed [in Prismic](https://prismic.io/), we use the Prismic API to fetch content and display it on the site.
* We have workflow systems that process new content before it's uploaded to the storage service. Currently we use [intranda's Goobi](https://www.intranda.com/en/digiverso/goobi/goobi-overview/) for digitised content and [Artefactual's Archivematica](https://www.archivematica.org/en/) for born-digital content. (repos: [goobi-infrastructure](https://github.com/wellcomecollection/goobi-infrastructure), [archivematica-infrastructure](https://github.com/wellcomecollection/archivematica-infrastructure))
* We make images available through [IIIF APIs](https://iiif.io/api/), an open standard used by many libraries and museums. Our IIIF services are provided by [Digirati](https://digirati.com/), and fetch images from the storage service. This includes both the APIs and the pre-processing required to make images available.
* Our account services allow users to manage [their library membership](https://wellcomecollection.org/pages/X_2eexEAACQAZLBi), and will allow them to order items from the library's closed stores (pending release).


---

# 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://docs.wellcomecollection.org/index/service-overview.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.
