Tool calling without handing over the keys.
Give agents useful tools while keeping permissions, approvals, and execution in your application.
Read the guideNeural Notes / Category
Builders field guides.
Turn broad ideas into clear contracts. Explore structured outputs, permissioned tools, purposeful chat memory, and versioned prompt templates.
The Builders collection is for readers ready to define how an application behaves. Begin with the contract your consumer needs: a reviewable record, an approved tool proposal, or a conversation that respects a correction. Then choose the guide that addresses that boundary. You do not need a live model connection to work through the initial design decisions.
Use the Pattern Lab to inspect the shape of a request and copy the reference material. Its examples are local fixtures, not a provider-specific SDK. The important work is adapting the intent, validation, and review requirements to your own application rather than copying field names without understanding them.
Each article includes difficult cases as well as the ordinary path. Test missing information, inconsistent evidence, revoked permissions, and a response that never arrives. Keep a small collection of these cases as you change prompts or model settings. The goal is a workflow whose errors remain visible, not a demonstration that looks flawless only on its first input.
Guides in this collection.
Build chat memory that knows its boundaries.
Separate session context, durable memory, and retrieved knowledge without losing user control.
Read the guide
Structured outputs: valid JSON is just the beginning.
Design output contracts that represent uncertainty, preserve evidence, and survive real inputs.
Read the guide
Prompt. Test. Repeat. A better template workflow.
Treat prompt changes as testable releases, with clear inputs, useful examples, and a rollback path.
Read the guideTake one idea into your own project.
Write a small example of the task, a result you would accept, and a result you would reject. Keep that example beside the guide as you read. The next track connects these concepts to a practical design boundary without requiring a provider account.
Continue the reading path