[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Events](/events) · [Live](/live)

[Help](/c/help/9)

# generateText: using web search with meta/muse-spark-1.1

5 views · 0 likes · 4 posts


Robert Groves (@rgroves) · 2026-08-30

The [meta.ai](https://meta.ai) doc notes that [search grounding](https://dev.meta.ai/docs/search-grounding) is available, and shows how to do it in one of its [example recipes](https://dev.meta.ai/docs/cookbook/search-grounding#turn-on-web-search).

I'm having trouble understanding how I would set that up via the ai-sdk's`generateText` method. I am using the Vercel AI Gateway as well, if that matters. What would I pass as the tools argument? Or do I need to pass something like provider specific options (e.g. using a `meta` key with config object)?

I did see that the Meta Model API is "drop-in compatible with the OpenAI SDK" (in the Meta [doc here](https://dev.meta.ai/docs/overview#call-the-api)), so I did try something like this:

```
import { openai } from '@ai-sdk/openai';

...

generateText({ 
  model: "meta/muse-spark-1.1",
  prompt: "...",
  ...
  tools: { web_search: openai.tools.webSearch() }
});
```

That did seem to work, but I wasn't quite sure if using the `openai.tools.webSearch` call was correct here for the meta model and I don't want to do something that is not documented as working but happens to work coincidentally.

Any guidance would be appreciated.


Robert Groves (@rgroves) · 2026-10-01

Well, the setup that I was previously able to get to work started to error out on September 23rd. All calls using meta/muse-spark-1.1 started failing with: \`Error \[GatewayInternalServerError\]: The web_search tool is not supported when Zero Data Retention is enabled.\`

The AI Gateway Settings dashboard shows that Zero Data Retention is not enabled though, so that's strange. I know it can be enabled per call as well, but I'm not doing that either. I have a support ticket open, but if anyone here is using muse spark with its built in search grounding successfully, would love to compare notes.


Robert Groves (@rgroves) · 2026-10-14

In case anyone lands here for similar reasons, here's the latest:

In the period between September 23rd and October 7th this was broken for currently unconfirmed reasons. It's working again since October 8th.

As for the why it broke, I've been back and forth with a helpful Vercel support team member and the latest is:

> ...it is on our team's radar. From our initial investigation, it looks like this may have been something that happened as a result of the model provider.


Robert Groves (@rgroves) · 2026-10-16

Final update from support:

> Meta has confirmed that as of last Friday, both image generation and web search are enabled (no longer blocked) for ZDR-enabled teams on the API. That matches what you saw: the errors came from a restriction on Meta’s side, and it has since been lifted. Your original setup with `meta/muse-spark-1.1` and the web search tool was correct all along, so you can keep using it as is. There’s no need to switch to the contributor model or to AI Gateway search tools unless you’d like to for other reasons.
>
> I’m sorry for the disruption this caused your workflow, and for the back and forth while we tracked down the cause. If you see this error come back, please reach out and we’ll jump on it right away.