Prepaid Tavily/Brave/Jina hop vs GSD search-the-web keys?

Summary

Offer a prepaid MCP meter for GSD search-the-web hops instead of provider API keys.

Problem to solve

GSD already ships a search-the-web extension (Tavily provider + Brave / Jina slots) so a long-running agent can leave the spec — adjacent: docker/.env.example still wants TAVILY_API_KEY / BRAVE_API_KEY / JINA_API_KEY for that hop.

Proposed solution

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

Alternatives considered

No response

Use cases

A long-running GSD agent can use a governed prepaid meter for search-the-web when Tavily/Brave/Jina retrieval is needed, without embedding separate provider keys.

Impact

The meter centralizes provider access, adds caps and a kill switch, and gives founding users +1,500 credits on the first successful call.

Evidence or prior art

No response

Additional information

No response