Classic Bitbucket Cloud projects fetch .circleci/config.yml using the Bitbucket OAuth credentials of a connected CircleCI user. Bitbucket applies the smaller per-user API budget (about 1,000/hour) to that identity. Bitbucket workspace / project / repository access tokens can get scaled limits (up to about 10,000/hour per Atlassian docs).
Request: let org admins attach a Bitbucket workspace access token (or equivalent non-user token) for config fetches / API calls used during pipeline creation, so trigger traffic uses the scaled limit instead of one user's OAuth budget. Also expose which identity each project currently uses for those calls.