Using search params opts the page out of the full route cache. I'd observe the output of the build command to see how next treats your page to learn whether it will be static or not. It is helpful when trying to utilize conflicting rules like generateStaticParams vs searchParams

You could however utilize fetch cache, to keep data cached, while still having searchParams in use for that page. Your page will still be rendered on the server, but responses from the api will be cached, causing much faster render.