# Intro

Each endpoint represents a content type from a given data provider, formatted according to our expected data structure in a JSON response. 

For each content type, the endpoint is not limited to one specific data provider. We can define multiple data providers for any given endpoint, and the specific data providers are merely a configurable on a per site basis. Our API proves to be a middle layer between all the various data providers, to ensure compatibility and ease of maintenance.

So, for example, the Faith Sourced website currently pulls the blog articles from the Posts API using a custom data provider. When this data provider is defined, the Posts API endpoint structures the data in the expected format of our React/Gatsby frontend, and it generates the entire website blog based on this data. \
\
Similarly, in a soon to be pushed update to the Faith Sourced website, it will pull all the site pages from the Pages API endpoint, and generate the entire sub page structure of the site, and the content therein.


---

# Agent Instructions: 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:

```
GET https://docs.faithsourced.com/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.