Laravel Keenable Laravel Package

Product Decisions This Supports

• Build vs. buy for web access: Lets the team buy search and page-fetch infrastructure instead of building crawlers, indexing, ranking, freshness handling, and extraction. Strong fit when web grounding is a supporting capability rather than the core product differentiator.
• AI feature roadmap: Enables agentic workflows, RAG-style retrieval, research assistants, source-backed answers, and “read this URL” features in Laravel applications with minimal integration work.
• Laravel AI SDK adoption: KeenableSearchTool and KeenableFetchTool reduce agent tooling work to configuration, which can accelerate prototypes and internal demos.
• Quality vs. freshness trade-offs: pro and realtime search modes plus date/time filters support product decisions around result quality, recency, and snippet length without custom search infrastructure.
• Cost and billing model decisions: API key, keyless public endpoints, and pay-per-request x402 paths give options for different deployment and monetization contexts, though each needs security and cost review.
• Operational reliability: Typed exceptions with rate-limit metadata and retryAfter() support better UX decisions for retries, backoff, and graceful degradation.
• Testing and delivery confidence: HTTP-client-based design means Http::fake() and Http::assertSent() work normally, lowering the cost of automated testing and CI coverage.

When to Consider This Package

Consider it when:

• You are building a Laravel 12/13 application on PHP 8.3+ and need web search or page-content retrieval for AI agents.
• You want a typed, Laravel-native client with DTOs, enums, and exceptions rather than hand-rolling HTTP calls.
• You are already using or evaluating the Laravel AI SDK and want ready-made search/fetch tools.
• You need both ranked search results and clean extraction from arbitrary URLs, including non-indexed pages.
• You want a fast pilot or MVP and are comfortable depending on an external API vendor.
• You need testable integration points and predictable error handling for rate limits, auth, credits, and validation failures.

Look elsewhere when:

• Search quality, ranking, or indexing is a core competitive differentiator that requires full control.
• You need self-hosted, air-gapped, or strict data-residency search infrastructure.
• You cannot send queries or URLs to a third-party API due to privacy, compliance, or contractual constraints.
• You are not on Laravel 12/13 or PHP 8.3+, or you need framework-agnostic PHP support.
• You require proven enterprise SLAs, mature vendor scale, or a long production track record; this is a first stable release.
• You need deep customization of crawling, extraction pipelines, or search ranking beyond the exposed modes and filters.

How to Pitch It (Stakeholders)

Executive summary: Keenable for Laravel is a low-integration way to add web search and page-reading capabilities to AI agents. It supports a buy-over-build decision: instead of standing up search infrastructure, the team can use a typed Laravel client and ready-made AI SDK tools to ship web-grounded features faster. The main trade-offs are vendor dependency, external data processing, per-request cost, and the fact that this is a new v1.0.0 release. Recommend a bounded pilot behind an internal interface, with cost monitoring, data-handling review, and fallback behavior for rate limits and API failures.