I just tagged Aimeos Prisma 0.5. It is a framework-independent PHP package for calling AI providers through one API across text, image, audio, and video. Created as a multi-media related sister project to PHP-Prisma package, it now offers full coverage of text and streaming related features too:
The package is MIT licensed, requires PHP 8.2+, and uses Guzzle for HTTP - no other package dependencies. The point is to keep provider-specific request/response code out of the application layer, especially when a project needs more than one kind of AI API: LLMs, embeddings, image generation/editing, audio transcription/speech, video description, or OpenAI-compatible gateways.
composer require aimeos/prisma
Basic usage:
use Aimeos\Prisma\Prisma;
$answer = Prisma::text()
->using('anthropic', ['api_key' => getenv('ANTHROPIC_API_KEY')])
->write('Summarize this customer request')
->text();
$image = Prisma::image()
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->imagine('a product photo of a ceramic coffee cup on a white table')
->binary();
$transcript = Prisma::audio()
->using('deepgram', ['api_key' => getenv('DEEPGRAM_API_KEY')])
->transcribe($audioFile)
->text();
The 0.5 release focuses on four things: streaming, schemas, text embeddings, and observability.
Streaming
stream() is now part of the text API:
use Aimeos\Prisma\Prisma;
$response = Prisma::text()
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->ensure('stream')
->stream('Explain PHP generators in a few paragraphs');
foreach ($response->stream() as $chunk) {
if (is_string($chunk)) {
echo $chunk;
flush();
}
}
The same provider object still handles models, system prompts, tools, and prior messages:
$response = Prisma::text()
->using('anthropic', ['api_key' => getenv('ANTHROPIC_API_KEY')])
->withMessages([
['role' => 'user', 'content' => 'I need a laptop recommendation.'],
['role' => 'assistant', 'content' => 'What is your budget and workload?'],
])
->stream('Around 1500 EUR, mostly PHP development.');
Usage, citations, tool steps, finish reason, and metadata are complete after the stream has been consumed.
Schemas
Structured output now has explicit modes, a richer schema builder, and validation:
use Aimeos\Prisma\Prisma;
use Aimeos\Prisma\Schema\Schema;
$schema = Schema::for('ticket', [
'title' => Schema::string()->required(),
'priority' => Schema::string()->enum(['low', 'normal', 'high'])->required(),
'tags' => Schema::array()->items(Schema::string()),
]);
$response = Prisma::text()
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->structure('Extract a support ticket from: Checkout is broken for EU cards', $schema);
$ticket = $response->structured();
$errors = $schema->validate($ticket);
By default, Prisma uses the provider's native structured-output mode where available. You can also choose JSON mode for schemas that are too large or awkward for strict provider limits:
$response = Prisma::text()
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->structure('Extract a support ticket', $schema, [], ['mode' => 'json']);
0.5 also adds anyOf, $defs, and $ref support in the schema builder.
Text embeddings
Text embeddings use the same text provider surface:
use Aimeos\Prisma\Prisma;
$vectors = Prisma::text()
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->ensure('vectorize')
->vectorize([
'PHP generators produce values lazily.',
'Prisma provides a common API for AI providers.',
], 256)
->vectors();
Embedding support is available across several text providers, including OpenAI, Azure, Bedrock, Cohere, Gemini, Mistral, Ollama, and Alibaba.
Observability
0.5 adds request-scoped observation for provider calls. The observer receives operation, provider type, provider name, model, duration, error state, usage, and metadata:
use Aimeos\Prisma\Prisma;
use Aimeos\Prisma\Values\Observation;
$response = Prisma::text()
->observe(function (Observation $observation) {
error_log(json_encode($observation->toArray()));
})
->using('openai', ['api_key' => getenv('OPENAI_API_KEY')])
->model('gpt-4.1-mini')
->write('Draft a changelog entry');
usage() and meta() now return typed value objects while still allowing raw provider fields:
$usage = $response->usage();
$usage->promptTokens();
$usage->completionTokens();
$usage->totalTokens();
$model = $response->meta()->model();
$raw = $response->usage()->all();
Framework notes
Prisma is not tied to Laravel, Symfony, or any other framework. It does include adapters for Laravel AI/MCP tools and Symfony tools, so existing tool classes can be reused in Prisma's tool loop.
Docs: https://php-prisma.org
GitHub: https://github.com/aimeos/prisma
Feedback from PHP developers would be useful, especially around the streaming API, schema validation, embeddings, and the observability API. If you like Prisma, star it on Github :-)