#Laravel AI Models

A companion package for the Laravel AI SDK (laravel/ai) that lists and caches the currently-available models for each provider you have configured. It reads your credentials straight from config/ai.php and keys everything on the SDK's own Laravel\Ai\Enums\Lab enum, so there's nothing to configure twice.

#Requirements

• PHP 8.3+
• laravel/ai ^0.7, ^0.8, ^0.9 or ^0.10

#Install

composer require lmsomeco/laravel-ai-models
php artisan vendor:publish --tag=ai-models-config       # optional
php artisan vendor:publish --tag=ai-models-migrations   # only if using database connectors

Any provider with credentials already set in config/ai.php is picked up automatically — no extra keys or env vars.

#Usage

#Artisan

php artisan ai:models                 # every configured provider
php artisan ai:models openai          # one provider (a Lab value)
php artisan ai:models --refresh       # bypass the cache
php artisan ai:models openrouter --json

#Facade / service

use Laravel\Ai\Enums\Lab;
use LmSomeco\AiModels\Facades\AiModels;

AiModels::all();                       // Collection<AiModel>
AiModels::provider(Lab::Anthropic);    // accepts a Lab or its string value
AiModels::configuredProviders();       // Collection<int, string> of provider names
AiModels::refresh();                   // clear all cached lists
AiModels::refresh(Lab::Groq);          // clear one

$model = AiModels::provider(Lab::OpenAI)->firstWhere('id', 'gpt-4o');
$model->provider;       // Laravel\Ai\Enums\Lab::OpenAI
$model->id;             // 'gpt-4o'
$model->contextWindow;  // int|null
$model->modalities;     // input modalities; [] when unknown
$model->outputModalities; // output modalities; [] when unknown
$model->raw;            // untouched provider payload

Registry methods return Laravel collections, so model properties and modality helpers can be used directly when filtering:

$models = AiModels::all()->filter(
    fn ($model) => $model->outputModalities === ['text'],
);

This strict form also excludes models whose output capabilities are unknown.

The ModelRegistry is resolvable from the container if you prefer DI over the facade.

#Provider coverage

See docs/extending.md for per-provider notes and how to add a resolver — contributions welcome.

#Documentation

• Installation — publish tags, env vars, how credentials are read
• Usage — the ai:models command and the full facade/DI API
• Database connectors — optional DB-backed provider configs
• Caching — cache keys, TTL and busting
• Extending — writing your own ProviderResolver

#License

MIT.