Prepaid Exa/Firecrawl hop vs Onlook web_search keys?

Onlook already ships a web_search client tool next to the visual editor — adjacent: apps/web/client/.env.example still wants EXA_API_KEY / FIRECRAWL_API_KEY so a design-time hop can leave the canvas.

I built apifare (formerly apipay) so that hop sits on a prepaid MCP meter instead: one bearer token; governed proxy; no Exa/Firecrawl keys in the Onlook env for those calls; caps + kill switch. Founding users get +1,500 credits on the first successful call.

Worth a look if a prepaid meter is what Onlook web_search spends, instead of the next Exa/Firecrawl key?