> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.pricelabs.co/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.pricelabs.co/_mcp/server.

# The Local-Intelligence Add-On

Works with recipes 01 · 03

Requires web search on

**What it does:** the surge dates in Recipes 01 and 03 arrive as bare percentages — "+9.3% on Aug 9–14" with no name on it. Paste this block at the end of either prompt's rules and the AI web-searches the reason behind every surge: the local festival, or — just as often — the school holidays of the country your guests fly in from. Validated in two markets: in France it named the exact festival behind the surge; in Indonesia it caught that the biggest surge was Australian school holidays plus China's Golden Week — something no local calendar would show.

**How to use it:** add the block below to the end of the recipe's prompt, and change the surge line of the Output to ask for the cause — e.g. Recipe 01's section 3 becomes: "Demand and price surge dates over the next 12 months, with their % — and for each, what's driving it (named event or feeder-market holiday)." Needs web search on in Claude (on by default).

## The add-on

Paste at the end of the recipe's rules:

**`Local Intelligence Add-on`**

```text Local Intelligence Add-on wordWrap
Local intelligence: for each high-demand window you find, use web search to identify what is driving it —
– search local events, festivals and holidays in [city/area] for those exact dates;
– also check the school-holiday and public-holiday calendars of this market's main visitor-origin countries — the biggest surges are often feeder-market holidays, not local events;
– for religious or moveable holidays, verify the dates for this specific year — never assume they match last year's;
– ignore any surge that starts on or right around today's date — that's a booking-curve artifact, not demand;
– name each event and its dates. If you find no explanation for a surge, say "cause unknown" — do not invent an event.
```

> **Pro tip**
>
> Keep the block's wording exactly as written — each line exists because a test
> run failed without it. The "those exact dates" anchor is what keeps the search
> from drowning in generic tourism pages.

**Goes well with:** [Market position](/mcp/cookbook/market-position) · [The full picture](/mcp/cookbook/full-picture)