Weave Code
Ai Generic Platform Laravel Package
symfony/ai-generic-platform
A generic platform bridge for Symfony AI that connects the framework's AI components to a common platform abstraction, simplifying configuration and enabling interoperable model integrations within Symfony applications.
Generic platform bridge for Symfony AI
Frequently asked questions about Ai Generic Platform
- How do I install symfony/ai-generic-platform in a Laravel application?
- Install it with Composer as a standalone dependency and bind the platform client through a Laravel service provider. The package is designed around AiClientInterface, so your application code should depend on that contract rather than on provider-specific classes. Because the package is pre-1.0, pin an exact version or gate minor upgrades behind tests.
- Can I use symfony/ai-generic-platform in Laravel without adopting the full Symfony framework?
- Laravel apps can consume the package as a standalone Composer dependency, but feasibility still hinges on whether your app already pulls Symfony components. Nothing in v0.14.0 adds or removes framework coupling. Expect some integration tax around container binding of AiClientInterface and translating Symfony AI exceptions into Laravel's handler.
- Which Laravel and PHP versions are supported by symfony/ai-generic-platform?
- The provided release notes and README excerpt do not list Laravel or PHP version constraints, so check the package's composer.json before installing. Because it is part of Symfony AI, it may pull Symfony components that determine the effective PHP floor. Validate the resolved dependency set in a staging branch rather than assuming compatibility.
- How do I bind AiClientInterface in Laravel's service container?
- Register a singleton or scoped binding for AiClientInterface in a Laravel service provider, resolving it to the generic platform client you configured. The evaluation notes container binding of AiClientInterface as part of the ongoing Laravel-Symfony integration tax, so keep the binding isolated in one provider. Also translate Symfony AI exceptions into Laravel's exception handler so failures surface correctly in logs and HTTP responses.
- What does Eden AI gateway support in v0.14.0 mean for Laravel apps?
- v0.14.0 adds an Eden AI gateway (feature #2417), and Eden AI is a multi-provider aggregator, so a Laravel app can reach many upstream models through a single adapter without provider-specific code. This improves the vendor-lock-in story and makes the which-provider question less blocking because one gateway credential can cover multiple vendors. It also introduces a second gateway configuration path for credentials, routing, and model naming, so validation and secrets management must cover it even if unused.
- How can I track AI token usage and cost per model in Laravel?
- v0.14.0 adds a model property on TokenUsage (#1566), which enables per-model cost calculation. You can persist usage per model and drive billing, per-tenant quotas, or budget alerts from a single table. Previously this required capturing the model name out-of-band, so cost visibility is now feasible in-app rather than only through provider dashboards.
- Is upgrading from 0.13.x to 0.14.x safe for a Laravel app?
- The v0.14.0 changelog contains no deprecations, removals, or configuration-surface changes, and the bug fixes are internal to tool-call handling, so the upgrade is low cost. Plan a Composer bump plus regression tests on any tool-calling paths. Because the package is pre-1.0, ^0.14 only permits 0.14.* patches and minor releases can carry breaking changes by convention, so pin exact versions or gate minor bumps behind a test run.
- Does symfony/ai-generic-platform handle tool calling correctly for agentic workflows?
- v0.14.0 includes two fixes (#2551 and #2543) that correct tool-call completion and stop-reason reporting, removing a silent-wrong-answer hazard for agentic workflows. If you built workarounds around tool calls being reported on stop finish reasons, plan to remove them after upgrading. Keep regression tests on tool-calling paths because these fixes are internal to tool-call handling.
- How should I test a Laravel integration with symfony/ai-generic-platform?
- The provided documentation does not describe dedicated testing utilities, so use Laravel's container to swap AiClientInterface for a fake or stub in feature tests. For the Eden AI gateway path, avoid live credentials in CI and assert your routing and model-name configuration separately. After the 0.14.x upgrade, add regression tests around tool-call completion and stop-reason reporting.
- What are the alternatives to symfony/ai-generic-platform for Laravel AI integrations?
- Alternatives depend on your constraints: direct provider SDKs or HTTP clients may be simpler if you do not already use Symfony components, while other Symfony AI platform bridges may fit if you want the same abstraction. The generic platform's main advantages are the AiClientInterface abstraction and Eden AI consolidation behind one adapter and credential. If latency or compliance makes an extra gateway hop undesirable, compare direct providers against the generic bridge before committing.
Weaver
How can I help you explore Laravel packages today?