​
Overview

Instructor offers a simplified way to work with LLM providers’ APIs supporting caching (currently only Anthropic API), so you can focus on your business logic while still being able to take advantage of lower latency and costs.

Note 1: Instructor supports context caching for Anthropic API and OpenAI API.

Note 2: Context caching is automatic for all OpenAI API calls. Read more in the OpenAI API documentation.

​
Example

When you need to process multiple requests with the same context, you can use context caching to improve performance and reduce costs.

In our example we will be analyzing the README.md file of this Github project and generating its structured description for multiple audiences.

Let’s start by defining the data model for the project details and the properties that we want to extract or generate based on README file.

<?php
$loader = require 'vendor/autoload.php';
$loader->add('Cognesy\\Instructor\\', __DIR__ . '../../src/');

use Cognesy\Instructor\Enums\Mode;
use Cognesy\Instructor\Features\Schema\Attributes\Description;
use Cognesy\Instructor\Instructor;
use Cognesy\Instructor\Utils\Str;

class Project {
    public string $name;
    public string $targetAudience;
    /** @var string[] */
    #[Description('Technology platform and libraries used in the project')]
    public array $technologies;
    /** @var string[] */
    #[Description('Features and capabilities of the project')]
    public array $features;
    /** @var string[] */
    #[Description('Applications and potential use cases of the project')]
    public array $applications;
    #[Description('Explain the purpose of the project and the domain specific problems it solves')]
    public string $description;
    #[Description('Example code in Markdown demonstrating domain specific application of the library')]
    public string $code;
}
?>

We read the content of the README.md file and cache the context, so it can be reused for multiple requests.

<?php
$content = file_get_contents(__DIR__ . '/../../../README.md');

$cached = (new Instructor)->withConnection('openai')->withCachedContext(
    system: 'Your goal is to respond questions about the project described in the README.md file'
        . "\n\n# README.md\n\n" . $content,
    prompt: 'Respond to the user with a description of the project with JSON using schema:\n<|json_schema|>',
);
?>

At this point we can use Instructor structured output processing to extract the project details from the README.md file into the Project data model.

Let’s start by asking the user to describe the project for a specific audience: P&C insurance CIOs.

<?php
$project = $cached->respond(
    messages: 'Describe the project in a way compelling to my audience: P&C insurance CIOs.',
    responseModel: Project::class,
    options: ['max_tokens' => 4096],
    mode: Mode::Json,
);
dump($project);
assert($project instanceof Project);
assert(Str::contains($project->name, 'Instructor'));
?>

Now we can use the same context to ask the user to describe the project for a different audience: boutique CMS consulting company owner.

Anthropic API will use the context cached in the previous request to provide the response, which results in faster processing and lower costs.

<?php
$project = $cached->respond(
    messages: "Describe the project in a way compelling to my audience: boutique CMS consulting company owner.",
    responseModel: Project::class,
    options: ['max_tokens' => 4096],
    mode: Mode::Json,
);
dump($project);
assert($project instanceof Project);
assert(Str::contains($project->name, 'Instructor'));
?>
Context cachingCustomize parameters of OpenAI client