# Lens Content APIs

Posts by profiles are scored (value between 0 and 1), classified (recommendable, maybe recommendable, not recommendable) and ranked every hour. The posts can then be retrieved by clients through any of the following 4 APIs. 

As an example, the `/feed` endpoint returns a JSON array of posts using the Popular algorithm as a default algorithm. To choose a different algorithm, specify the algorithm as a path parameter. 

Let's walk through all the **Global** and **Personalized** content feed recommendation APIs next.

## Global Feed

As for generalized (non-personalized) feed of posts according to each algorithm, we now have the following pre-computed algorithms.  These algorithms are:

* `/feed/recent` to choose the Recent algorithm. 
* `/feed/popular` to explicitly choose the Popular algorithm.
* `/feed/recommended` to choose the Recommended algorithm.
* `/feed/crowdsourced` to choose the Crowdsourced algorithm.

In addition to the algorithm path parameter, the endpoint also takes an optional `limit` query parameter. All the algorithms return a **max of 100 posts**. To get a smaller set of posts, specify the limit parameter. Example: `/feed/recent?limit=10`

## Personalized Feed

Personalized content feed algorithms are meant to generate lists of posts that are most relevant to each user. These algorithms crawl a user's social graph and activity when recommending posts.  There's a time decay element in this as well.  

These algorithm deployed is:

* `/feed/personal/{profile}/following` which uses the Following strategy

In addition to the algorithm path parameter, the endpoint also takes an optional `limit` query parameter. All the algorithms return a **max of 100 posts**. To get a smaller set of posts, specify the limit parameter. Example: `/feed/personal/karma3labs.lens/following?limit=10`

## API Documentation

{% hint style="info" %}
Tryout the APIs here! — [https://openapi.lens.k3l.io](https://openapi.lens.k3l.io/#/default/getScores)
{% endhint %}

{% openapi src="<https://raw.githubusercontent.com/Karma3Labs/ts-lens/main/server/openapi/openapi.yaml>" path="/feed/personal/{profile}/{strategy}" method="get" expanded="false" %}
<https://raw.githubusercontent.com/Karma3Labs/ts-lens/main/server/openapi/openapi.yaml>
{% endopenapi %}

{% openapi src="<https://raw.githubusercontent.com/Karma3Labs/ts-lens/main/server/openapi/openapi.yaml>" path="/feed/{strategy}" method="get" expanded="false" %}
<https://raw.githubusercontent.com/Karma3Labs/ts-lens/main/server/openapi/openapi.yaml>
{% endopenapi %}

You can try out this API at this **OpenAPI interface** — [https://openapi.lens.k3l.io](https://openapi.lens.k3l.io/#/default/getPersonalFeed)


---

# 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.openrank.com/integrations/lens-protocol/lens-content-apis.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.