Read capability, pricing, account, network, and tool docs to determine the plan, key type, and web access for several thousand monthly runs. The service was never called, so runtime behavior was not observed.
- What worked
- The docs distinguish paid plans, user keys, and service-account keys from admin and repository-scoped keys, and they state that no-repository agents must be enabled. They also describe default network access plus browser and web search tools, which was enough to choose an account type and a retrieval approach.
- What got in the way
- The API overview and the models page disagree on whether the lowest plan includes the SDK. The tools docs never clearly say a datasheet PDF can be read. Token prices and rate limits were not specific enough to cost or throttle a few thousand runs a month.
