3 ideas?

[christopherarter]

Yo! I have two three ideas and wanted to share them to get thoughts:

Default Model

Would there be interest in a PR to the PrismManager class that passes in an optional default_model param to the factory methods?

// config/prisim.php
        'anthropic' => [
            'api_key' => env('ANTHROPIC_API_KEY', ''),
            'version' => env('ANTHROPIC_API_VERSION', '2023-06-01'),
            'default_model' => env('ANTHROPIC_DEFAULT_MODEL'),
        ],

Fluent helper

   prism()->text()->using(..); // etc

which would just be something like this under the hood:

use \EchoLabs\Prism\Prism;

function prism(): Prism {
  return app(Prism::class);
 }

Schema Decorators

I love the builder style around making schemas. Perhaps decorators like this would be possible to create schema definitions as DTOs:

class Location extends Data {
  
  #[ObjectSchema(Country::class)]
  public Country $country;

   #[StringSchema(description: 'the street address detected in the text. Use correct street name captilaization')
    public string $streetAddress;
}

Just off the top of my head it looks like this could potentially require a union type for the withSchema method but just an idea.

[sixlive]

Love the idea of a functional fluent helper!!! I also really wanted to do Schema Decorators, have just prioritized other stuff. Honestly, kind of on the fence about default models, not completely opposed to it.

For Decorators I was kind of thinking about using either a union type OR a new method ->asObject(Location::class). Then when we cast the PendingRequest to a Request we would just do some validation on ensuring only either withSchema or asObject is used.

[christopherarter]

Would you entertain a little fluent helper PR? I definitely would love to help 🤘

[sixlive]

Absolutely! Would love that!

[ChrisB-TL]

Love the idea of Schema DTOs.

And also allow a define method, for messier schemas.

E.g. deeply nested schemas and schemas with long descriptions.

(P.S. using schema descriptions as mini prompts is low key amazing!)

[christopherarter]

Yeah I hand rolled this approach once with Spatie Data and a PHP to JSON Schema package and it worked beautifully for consistent responses. I suppose theres no reason someone couldn't just extend the ObjectSchema class and define the properties there, but it's nice to use existing app DTO types. So if you're using it elsewhere, just add decorators and it's now a response contract too.