An SDK is a promise to keep something working across versions, which is why publishing one before the API surface has settled is a promise you break on your own users. There is no published SDK yet and this page does not show a package name that does not resolve.
Types that match the API, authentication handled once, pagination and retries that behave sensibly, and errors that arrive as something you can branch on. None of that is difficult; all of it is a maintenance commitment.
A library published against a surface that is still moving forces a choice between breaking users and freezing the API. Waiting until v1 is genuinely stable costs early adopters some convenience and costs everybody else far less.
The HTTP surface is complete and directly usable. A bearer token and any HTTP client is the whole integration story today, and code written that way keeps working when a library appears.
Not published. No package exists under any registry, and any package claiming to be an official GRAJ SDK today is not one.