SDKs

Two clients, TypeScript and Python. Both are thin: a typed client for every call in the API reference, plus three helpers that mirror what an assistant does, so search, describe, and act are one line each.

Neither package is published yet. Through the beta both run from source, and each page says exactly how. When they are published, those pages change and nothing else does.

If you would rather not take a dependency at all, everything the SDKs do is a POST with a JSON body. API reference has the whole convention.

What is the same in both

One key, one project. The key goes on the client at construction, not on each call. Every request carries it, and the project it resolves to is what scopes everything you read and write, so no request body names a project.

Construction fails loudly. An empty key or an address that is not http or https raises at construction rather than on the first call, so a misconfigured deployment fails at startup.

The person is separate from the key. Every call names the person it acts for. One key serves everybody in your project, and each person's connected accounts are theirs alone.

A refusal is a return value. A destructive call with no confirmation, a call parked on an approval, a rate ceiling: all of these come back as a normal answer whose status says what happened. They are not exceptions. Exceptions are for the request never arriving. See Error codes.

The naming follows the language. Methods are camelCase in TypeScript and snake_case in Python; fields follow the contract in both.