Pydantic AI

An agent is configured with a model, instructions, tools and an expected output type. Pydantic-based validation checks whether returned data conforms to the declared structure; tool signatures and dependency types help organize application integration. Validation feedback can be used in retries when a model returns an unacceptable shape. The framework also supplies execution and observability facilities around the interaction. This differs from a model merely being asked to emit JSON: the application has an explicit contract it can enforce. A valid object, however, can still contain a wrong fact or an action outside the user's authority.

The practitioner defines output models with meaningful constraints, provides dependencies through the execution context and keeps tool responsibilities narrow. Validation errors should be actionable, and retry budgets should prevent endless attempts at an impossible contract. Useful results include typed outputs, clear error handling and traces that connect validation to subsequent model behavior. Evaluation covers valid but incorrect objects as well as malformed outputs, checking that business rules and external permissions are enforced by ordinary application code where appropriate.

Strong typing reduces certain integration errors but does not make model judgments type-safe in a broader semantic sense. Overly permissive fields can admit meaningless content, while restrictive schemas can force uncertain information into an apparently complete object. Retry behavior must not conceal unresolved extraction uncertainty. Quality combines meaningful types, independent business checks and honest representation of missing values. Version changes can affect interfaces, so dependencies and provider-specific output behavior need testing in the actual application environment.