We were getting some odd type aliases on the TypeScript side because Pydantic generated JSON Schema with fields like this:

{
  "given_name": {
    "title": "Given Name",
    "type": "string"
  }
}

json-schema-to-typescript turns this into:

type GivenName = string;

and then uses that as a type alias. The party line from both projects is that they're both doing this correctly (see bcherny/json-schema-to-typescript#504 and pydantic/pydantic#1740), however pydantic seems to recognize that this may not be what everyone wants and provides example code to strip off title in their docs:

"For example, the title key can be removed from the model's properties:"
https://docs.pydantic.dev/latest/usage/schema/#schema-customization

We can define our own base model to use this in all our API types.