# NEARWEEK

## THE ORIGIN OF NEARWEEK

\
NEARWEEK started out as a weekly newsletter covering everything within the NEAR PROTOCOL ecosystem. The #number of each nearweek reflects the unbroken chain of NEARWEEK killing streaks of pushing the newsletter out every week. With each edition we seek to improve not only the format of the newsletter, but also adding other content types such as daily newsletters, native blogposts, X threads, X Spaces and the list goes on.

<div align="left"><figure><img src="https://876180945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrhVl9WVzc48Q5wxErKFj%2Fuploads%2FwbQ2LaDfhUkQgma9NvFc%2FmsOLWbog_400x400.jpg?alt=media&#x26;token=884a92ec-0513-4d20-8607-05ec76e8b895" alt=""><figcaption><p>Ser, before we start, make sure to subscribe to the weekly newsletter!</p></figcaption></figure></div>

### 📩 [Subscribe to the weekly NEARWEEK newsletter](https://subscribe.nearweek.com/)


---

# 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.nearweek.com/start/nearweek.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.