Add JigsawStack toolkit with 18 AI SDK tools

[pushpak1300]

Currently the toolkit covers web search via Tavily, but there's no integration for JigsawStack's AI APIs. This adds a single shipfastlabs/toolkit-jigsawstack package exposing all 18 tools from JigsawStack's AI SDK integration (sentiment, summary, embedding, prediction, text-to-SQL, text/image translation, web search, AI scrape, HTML-to-any, search suggestions, vOCR, object detection, speech-to-text, and the NSFW/profanity/spell/spam validators).

Register them the same way as Tavily:

use Shipfastlabs\Toolkit\JigsawStack\JigsawStack;

$tools = JigsawStack::all(); // Collection<int, Tool>

or pick individual ones:

use Shipfastlabs\Toolkit\JigsawStack\JigsawStackWebSearch;
use Shipfastlabs\Toolkit\JigsawStack\JigsawStackSentiment;

$tools = [new JigsawStackWebSearch, new JigsawStackSentiment];

Notes

• Structure mirrors the Tavily package: one mirror, a JigsawStack::all() helper, and a shared InteractsWithJigsawStack trait for the HTTP call and error handling so each tool stays tiny.
• API key is read from config('services.jigsawstack.key') (sent as the x-api-key header), documented in the package README.
• Tools return errors to the model as strings and never throw, per the toolkit conventions.
• Added the package to the coverage gate; it's at 100% (PHPStan max, type + code coverage), composer test green.
• Wired into the workbench agent so you can try it with vendor/bin/testbench agent:run "..." once JIGSAWSTACK_API_KEY is set.

Descriptions are authored to match the AI SDK tool set since JigsawStack's SDK doesn't expose literal description strings. Open to tweaking wording.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
toolkit	Ready	Preview, Comment	Jun 7, 2026 7:29pm