The pot calling the kettle black.

Will this be compatible with graphql?

It won't break GraphQL, as it uses POST. It can very much improve it if adopted: - use QUERY method when querying resources - use POST method for mutations