Weave Code
Ai Amazee Ai Platform Laravel Package
symfony/ai-amazee-ai-platform
Symfony AI bridge for the amazee.ai Platform. Connect Symfony AI to LiteLLM proxy endpoints and OpenAI-compatible providers through amazee.ai, enabling centralized AI access and management. Links to docs, issues, and contributions in the main Symfony AI repo.
amazee.ai LiteLLM platform bridge for Symfony AI
Frequently asked questions about Ai Amazee Ai Platform
- What is symfony/ai-amazee-ai-platform used for?
- It is a Symfony AI bridge that connects your application to the amazee.ai Platform, which exposes LiteLLM proxy endpoints and OpenAI-compatible providers. It lets you route chat and streaming requests through amazee.ai instead of calling each AI provider directly. The package builds on Symfony AI's ClientInterface and provider abstraction so you can switch models through configuration.
- How do I install symfony/ai-amazee-ai-platform with Composer?
- Install it with Composer alongside the Symfony AI bundle, for example composer require symfony/ai-amazee-ai-platform. The package is intended for Symfony 7 and later with the symfony/ai bundle installed. After installation, register the provider in your Symfony AI configuration and supply your amazee.ai API key through an environment variable.
- How do I configure the amazee.ai provider in Symfony?
- Add a provider entry under symfony_ai in config/packages/symfony_ai.yaml, pointing the client at amazee.ai and reading the key from an environment variable such as AMAZEE_AI_KEY. You can also declare a default model and a fallback model so requests degrade gracefully. If you use custom providers, register the service in your Symfony service configuration.
- Which Laravel versions does this package support?
- The package is not natively Laravel-compatible because it is built around Symfony's service container, ClientInterface and provider abstractions. Laravel's container and service registration order differ, so you generally need a custom service provider or facade to wrap the Symfony client. There is no official Laravel integration documented for this bridge.
- Can I use symfony/ai-amazee-ai-platform in a Laravel application?
- It is possible but requires glue code, since the package assumes Symfony's container and event system. A common approach is to register the Symfony client in a Laravel service provider and expose it through a facade, or to call the LiteLLM proxy endpoints directly with Laravel's HTTP client. Streaming responses may need adaptation because the bridge returns DeltaInterface objects rather than raw JSON chunks.
- How does model routing and fallback work with amazee.ai?
- Configuration lets you set a default model and a fallback model, and amazee.ai routes each request to the appropriate OpenAI-compatible provider behind its LiteLLM proxy. This means you can switch between providers such as OpenAI, Anthropic or Mistral without changing application code. Fallback logic can also help control costs when a cheaper model is acceptable.
- Does this package support streaming responses?
- Yes, the bridge uses Symfony AI's DeltaInterface to deliver typed streaming deltas instead of raw JSON chunks. That improves type safety for real-time features such as chatbots. If you are integrating outside Symfony, your streaming handler must be able to consume these delta objects.
- What are the risks of depending on amazee.ai and LiteLLM?
- Requests go through the amazee.ai LiteLLM proxy, so availability, rate limits and pricing are governed by that third-party service. The proxy also adds some latency compared with calling providers directly, which matters for latency-sensitive applications. Evaluate your SLA requirements and consider benchmarking before committing in production.
- Is symfony/ai-amazee-ai-platform production ready?
- It is an early-stage package with very low adoption and active development, so expect potential breaking changes between releases. Pin versions in Composer and review changelogs before upgrading. For critical systems, plan for extra testing and consider whether direct provider integration is a safer short-term option.
- Are there alternatives to using this bridge for multi-provider AI access?
- Alternatives include using Symfony AI with other provider bridges, calling provider APIs directly through an HTTP client such as Guzzle, or integrating the LiteLLM proxy yourself without the Symfony bridge. If multi-provider routing and centralized key management are core requirements, amazee.ai remains a reasonable fit. If you only need one provider, a direct integration is usually simpler.
Weaver
How can I help you explore Laravel packages today?