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

# spot registry

20 breaks, north to south. Use `spot_key` as the `loc` parameter.

| spot\_key            | Break              | Area                               |
| -------------------- | ------------------ | ---------------------------------- |
| `tamri`              | Tamri              | North of Taghazout                 |
| `dracula`            | Dracula's          | North coast                        |
| `boilers`            | Boilers            | North coast                        |
| `killer-point`       | Killer Point       | North of Taghazout                 |
| `mysteries`          | Mysteries          | North of Taghazout                 |
| `la-source`          | La Source          | Between Taghazout and Killer Point |
| `anchor-point`       | Anchor Point       | North Taghazout                    |
| `hash-point`         | Hash Point         | Taghazout                          |
| `taghazout`          | Taghazout Bay      | Taghazout                          |
| `panorama`           | Panorama Point     | South Taghazout                    |
| `banana-point`       | Banana Point       | Aourir                             |
| `devils-rock`        | Devil's Rock       | Tamraght                           |
| `cro-cro`            | Cro-Cro            | Tamraght coast                     |
| `tamraght`           | Tamraght           | Tamraght                           |
| `km11`               | KM11               | Coast road south of Tamraght       |
| `km12`               | KM12               | Coast road south of Tamraght       |
| `anza`               | Anza               | Agadir                             |
| `agadir`             | Agadir Beach       | Agadir                             |
| `imsouane`           | Imsouane Bay       | Imsouane                           |
| `imsouane-cathedral` | Imsouane Cathedral | Imsouane                           |

## Machine-readable

A CSV of this registry — including the forecast page and feed URL for each break — ships with the [taghazout-surf client](https://github.com/MyTaghazout/taghazout-surf) and is published as a dataset on [Hugging Face](https://huggingface.co/datasets/MyTaghazout/taghazout-surf-spots).

## Choosing a break

{% hint style="info" %}
No API field can tell you this: these breaks are not interchangeable.
{% endhint %}

* **The points** (Anchor Point, Killer Point, Boilers, Mysteries) are fast right-handers over rock, and they get crowded when there is swell. They are not beginner waves.
* **The beach breaks** (Devil's Rock, Croco, Panorama on a small day) are where people learn here.
* **Imsouane Bay** is the long, slow, forgiving one — the longboard day.

Season on this coast runs roughly November to March, and a 3/2 mm wetsuit covers most of the year.


---

# 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://taghazout.gitbook.io/taghazout-docs/spot-registry.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.
