# Content Service

The Content service uses the Graph engine to communicate with Neo4j. The Graph engine expects schema definitions for each object type. It validates the data object with the object definition during various CRUD operations.

Below are the details of the other services that are included in the package along with content-service

{% content-ref url="/pages/dIP0JimPOU7lBPSSYXO6" %}
[Collection APIs](/learn/product-and-developer-guide/content-service/content-service-1.md)
{% endcontent-ref %}

{% content-ref url="/pages/KB6eUYGkKp02jcC1h3i4" %}
[Media APIs](/learn/product-and-developer-guide/content-service/content-service-2.md)
{% endcontent-ref %}

{% content-ref url="/pages/CIli54TKFD1LSCXEfCSw" %}
[Channel APIs](/learn/product-and-developer-guide/content-service/channel-service.md)
{% endcontent-ref %}

{% content-ref url="/pages/JXX0NtvBhCsuTHb9YcJM" %}
[License APIs](/learn/product-and-developer-guide/content-service/license-service.md)
{% endcontent-ref %}

{% hint style="info" %}
As part of the product roadmap, the Collection, Media, Channel, and License APIs mentioned above will be moving out from the content-service.
{% endhint %}


---

# 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://knowlg.sunbird.org/learn/product-and-developer-guide/content-service.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.