IntentKit’s skill keys still treat Tavily + Jina as the primary web_search backends (TAVILY_API_KEY / JINA_API_KEY; optional FIRECRAWL_API_KEY) so an agent can leave the box.
I built apifare (formerly apipay) so that hop sits on a prepaid MCP meter instead: one bearer token; governed proxy; no Tavily/Jina/Firecrawl keys in .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 IntentKit spends on web_search, instead of the next skill key?
IntentKit’s skill keys still treat Tavily + Jina as the primary
web_searchbackends (TAVILY_API_KEY/JINA_API_KEY; optionalFIRECRAWL_API_KEY) so an agent can leave the box.I built apifare (formerly apipay) so that hop sits on a prepaid MCP meter instead: one bearer token; governed proxy; no Tavily/Jina/Firecrawl keys in
.envfor 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 IntentKit spends on web_search, instead of the next skill key?