Weave Code
Laravel Laravel Package
papi-ai/laravel
Laravel integration for Papi AI that connects your application to AI services with minimal setup. Includes a service provider, configuration options, and a clean, expressive API for sending prompts and handling AI responses from anywhere in your Laravel app.
papi-ai/laravel is a lightweight AI integration package for Laravel that gives your application a clean, expressive interface for sending prompts to AI providers and working with their responses. It wraps provider APIs behind familiar Laravel patterns—configuration files, facades, and service container bindings—so you can add AI-powered features without scattering raw HTTP calls across your codebase.
- Fluent API for building and dispatching prompts
- Config-driven providers with credentials managed through
.env - Laravel-native architecture using facades, bindings, and publishable config
- Structured responses returned as objects for predictable handling
- Extensible design for adding custom providers or request middleware
Frequently asked questions about Laravel
- What is papi-ai/laravel and what does it do?
- papi-ai/laravel is a Laravel bridge package for the PapiAI AI agent library, giving Laravel applications access to the agent functionality exposed by the underlying papi-core package. It is not a standalone AI library; it is a thin integration layer that depends on papi-core 0.15.3 or higher. The package is currently at version 0.15.1 and is considered early-stage, with minimal adoption and limited documentation. Treat it as a convenience wrapper rather than a full-featured AI framework.
- How do I install papi-ai/laravel with Composer?
- Install it with composer require papi-ai/laravel, which will resolve the papi-core 0.15.3 constraint transitively. Before running the command, confirm your root composer.json permits papi-core at that version and that nothing else in your dependency tree conflicts with it. The release notes do not disclose any service provider or configuration publishing steps, so check the package's own README and composer.json after install. Running the install in a scratch branch first lets you see exactly which other packages move in composer.lock.
- Which Laravel and PHP versions does papi-ai/laravel support?
- No supported Laravel or PHP version matrix is disclosed in the package's release notes or overview, which is a significant gap for planning. The only stated requirement is the transitive dependency on papi-core 0.15.3 or higher. The practical answer is to read the require section of the package's composer.json before committing to any work, since that file defines the actual constraints. Until that is verified, assume nothing about framework or runtime compatibility.
- Do I need to install papi-core separately to use this package?
- No, you do not install it manually, but you will get it regardless because papi-ai/laravel declares a hard dependency floor on papi-core 0.15.3. This makes adoption a decision about adopting papi-core too, since the two packages must be tracked in lockstep at 0.x release cadence. If your application already consumes papi-core elsewhere, adding this bridge is low friction. If it does not, you are taking on a second dependency surface to maintain and monitor.
- Is papi-ai/laravel production-ready?
- No, it is best treated as experimental at this stage. It is pre-1.0 at version 0.15.1, has minimal adoption, and ships with limited documentation and no changelog covering the 0.1.0 to 0.15.0 range. At 0.x, a minor version bump can legitimately include breaking changes, so the public API carries no stability guarantee. Use it to prototype AI agent flows, and only sequence it into a production application after you have validated the version alignment and test coverage yourself.
- Will upgrading papi-ai/laravel break my application?
- It can, and the most likely cause is not this package itself but the papi-core version floor it drags in. Because it requires papi-core 0.15.3 or higher, an update can pull other packages forward in the dependency tree, and that movement is invisible from this package's own release notes. Plan the papi-core bump as its own change with its own test pass, then update this package separately, and do not bundle either with unrelated work. Pre-1.0 semver means you should treat every release as potentially breaking until proven otherwise.
- Does papi-ai/laravel support PHP 8.5?
- The PHP 8.5 compatibility fixes associated with this release are delivered by papi-core 0.15.3, not by the bridge package itself, so the bridge inherits them transitively. That only matters if PHP 8.5 is actually on your roadmap. If your fleet runs PHP 8.2 or 8.3, this release is close to a no-op and the urgency is minimal; if a PHP 8.5 upgrade is imminent, the dependency bump is a prerequisite and should land and soak before the runtime moves.
- How should I test papi-ai/laravel before adopting it?
- Stand the package up in a scratch branch or a throwaway Laravel app first rather than in your main application. Resolve papi-core at its 0.15.3 floor there and observe exactly what else changes in composer.lock, since dependency drift is the most likely source of surprise regressions. Once it is running, exercise the AI agent calls your application would actually make, then run your full suite plus any integration tests that touch the API surface before deciding whether to sequence it into the main codebase.
- Is there a changelog or documentation for papi-ai/laravel?
- There is no changelog published for the 0.1.0 to 0.15.0 range, no documented feature set, and no stated supported PHP or Laravel matrix. The available information amounts to the package overview and release notes, which is thin evidence for any adoption decision. In practice, your best sources are the repository's README, its composer.json, and the papi-core package it wraps. Any assessment built on the current notes should be treated as low confidence.
- What are the alternatives to papi-ai/laravel for AI agents in Laravel?
- The main alternative is to use papi-core directly without the Laravel bridge, which removes one dependency from your tree but means wiring configuration and service bindings yourself. Beyond that, you can evaluate other Laravel AI agent packages with a 1.0 or better-established release history and a documented Laravel and PHP support matrix. The deciding factor here is whether your team already consumes papi-core: if it does, this bridge is low friction, and if it does not, the coupling and dual release cadence are the real cost you are weighing against alternatives.
Weaver
How can I help you explore Laravel packages today?