Weave Code
Ai Albert Platform Laravel Package
symfony/ai-albert-platform
Symfony AI platform bridge for Albert, the French government's OpenAI-compatible LLM API (OpenGateLLM). Wire Albert models into your Symfony apps for chat and completions alongside other Symfony AI platforms.
Albert platform bridge for Symfony AI
Frequently asked questions about Ai Albert Platform
- What is symfony/ai-albert-platform and what does it do?
- It is a Symfony AI platform bridge that connects Albert, the French government's OpenAI-compatible LLM API (OpenGateLLM), to Symfony AI's provider abstraction. The package itself is a thin adapter: provider routing and model abstractions live in symfony/ai, and this bridge maps Albert's HTTP endpoints onto them so you can use Albert models for chat and completions. It is installable with Composer in any PHP project, including Laravel, but it is a seam rather than a full solution.
- How do I install symfony/ai-albert-platform in a Laravel application?
- Run composer require symfony/ai-albert-platform alongside symfony/ai, then bind the Albert platform into Laravel's service container from one of your own service providers. Read the API key and base URL from environment configuration and resolve the platform through your own gateway interface rather than injecting it into domain code. There is no package:discover step specific to this bridge, so installation is plain Composer plus manual wiring.
- Does this package ship a Laravel service provider, facade or publishable config file?
- No. It contains no Laravel-specific glue: no service provider, no config publishing, no facade, and no queue or Eloquent integration. Every ergonomic piece a Laravel developer expects is work you own, typically under a day to wrap, but treat that wrapper as a permanent maintenance surface. Keeping the bridge behind your own interface boundary also limits the blast radius of future 0.x changes.
- Which Laravel and PHP versions does symfony/ai-albert-platform support?
- The package is framework-agnostic, so its real constraints are the PHP and symfony/ai versions declared in its composer.json rather than a Laravel version. Any modern Laravel application running a compatible PHP version can install it because it is PSR-4 autoloadable and has no framework coupling. Check composer.json before upgrading and pin the bridge version in your lock file, since 0.x minor bumps may legally contain breaking changes.
- Does it support chat completions and embeddings?
- Yes. It supports chat and completions against Albert models, and embeddings have been explicitly supported since v0.4.0. Be aware that OpenAI compatibility does not mean feature completeness, so validate streaming and tool or function calling against OpenGateLLM before you depend on them. Contract tests against a recorded fixture set are the cheapest way to catch gaps early.
- What is the carbon footprint metadata added in v0.14.0?
- v0.14.0 exposes Albert's carbon footprint as result metadata, an additive field riding the existing response path rather than a new abstraction or integration surface. Model it as a nullable attribute on your own result DTO instead of a first-class concern. The package surfaces a value but documents no methodology, so decide internally whether and how you are allowed to report on it.
- Can I reuse my existing OpenAI PHP code with Albert?
- Because Albert is OpenAI-compatible, the conceptual migration from openai-php style code is small, and the practical migration stays small if you keep an internal interface boundary. Do not let vendor-specific calls leak into domain code, or switching providers later becomes a refactor instead of a config change. Expect some feature gaps relative to OpenAI, particularly around streaming and tool calling.
- Is symfony/ai-albert-platform production ready and actively maintained?
- It is an early-stage 0.x package with low adoption, but recent releases are credited to an upstream Symfony AI maintainer, which suggests it is tracked rather than abandoned. The v0.14.0 carbon metadata addition is the first genuinely new user-facing capability in several releases, which is encouraging but not a guarantee. Pin versions, wrap the adapter in your own gateway, and treat it as de facto single-vendor, upstream-tracked maintenance.
- How do I handle retries, timeouts, rate limits and streaming with Albert?
- You own all of that: timeouts, retries with jitter, circuit breaking, 429 and quota handling, structured logging, token accounting, and prompt or response redaction. Streaming support depends on what OpenGateLLM cleanly provides, so verify it against the API reference before designing around it. Implement these concerns in your gateway layer so domain code never talks to the Albert bridge directly.
- How should I test an Albert integration, and can I fail over to other providers?
- Record a fixture set and run contract tests against it so a response-shape change from OpenGateLLM fails your build instead of production. Swap the platform for a test double behind your own interface so unit tests never hit the network. Because Symfony AI provides the provider abstraction, you can register another platform as a fallback from day one, which mitigates Albert's niche catalogue and unknown quotas.
Weaver
How can I help you explore Laravel packages today?