Maybe a stupid question, but what's the purpose of the [build graphql api](https://www.prisma.io/docs/get-started/03-build-graphql-servers-with-prisma-JAVASCRIPT-e001/) section of the docs? i thought the point of prisma was that it auto-generated the graphql api out of your schema? the localhost:4000 graphql api loses access to all the cool auto generated shit that localhost:4466 has. is there some reason i shouldn't be hitting the auto-generated api?

Depends on your use case - for prototyping using the prisma endpoint directly might be acceptable, but you probably don't want it to be open to the public, since it is after all just an abstraction layer over your database, ergo everyone who knows the endpoint can hit all of the queries and muations, which you probably want to avoid, especially when dealing with userdata and/or content