Registry integration proposal: extension/nimble (governed web search + extract)

What problem are you trying to solve?

eve agents need live web data, and the registry has no way to install it. Across the current 83 items in https://eve.dev/r/registry.json, none is a web search or page extraction provider.

The closest items solve a different problem. extension/browserbase, extension/kernel, extension/agent-browser, and connection/browser-use are browser automation, where you drive a session to act on a page. connection/similarweb is market analytics, not retrieval. None answers "search the open web and hand the agent clean, current content."

defineTool overrides for web_search and web_fetch are the documented way to supply your own retrieval, and no registry item installs one.

Per CONTRIBUTING.md#extension-requirements, opening this to ask for maintainer agreement before submitting a registry PR.

Proposed solution

Add extension/nimble, Nimble web search and extraction as a reviewed extension. The package is @nimble-way/eve, Apache-2.0, source at Nimbleway/eve. It's built around the three things that break agents retrieving from the web:

• Stale answers are invisible. Nimble retrieves in real time, navigating sites and rendering JavaScript on request rather than serving a pre-built index, so the agent gets the page as it is now.
• Retrieval is usually unauditable. Every run produces a Search Plan recording what was searched, where, and why, so a wrong answer is debuggable. That matters in a framework where runs resume and replay. Nimble operates under SOC 2, GDPR, and CCPA.
• Raw pages are a large avoidable token cost. Retrieval returns what was asked for instead of HTML for the model to parse, so runs use fewer steps and less context.

It mounts nimble__search, nimble__extract, a resumable pair for longer research, and a web-research skill, plus documented one-line web_search / web_fetch override recipes. One-file mount, a single NIMBLE_API_KEY, nothing else required.

It's publicly installable from npm and documented for configuration, authentication, and security-sensitive behavior at docs.nimbleway.com/integrations/connectors/vercel-eve.

If there's maintainer appetite, I'll submit the PR per the "Adding an integration to the registry" guide. Happy to hand over the item JSON, gallery copy, and logo instead if you'd rather author it directly.

Alternatives considered

Users can npm i @nimble-way/eve and hand-write the mount today, and we can self-host a shadcn-format registry with no action on your side, so distribution isn't blocked. The ask is discoverability and the review bar users expect from the official gallery.

We also considered a connection/ item over Nimble's hosted MCP server, which works today with zero Nimble code. The extension shape fits better because the override recipes and the research skill are most of the value, and a connection can provide neither.

Start with CONTRIBUTING.md#extension-requirements and the current registry.json to understand the integration requirements and item structure. Review the linked Nimble package and its configuration, authentication, and security documentation before seeking maintainer agreement. Done means an accepted registry proposal followed by a compliant PR containing the extension item, gallery copy, and logo.