Are you measured by the number of API calls or overall token usage?

If the latter, do everything you can to stuff the context window with as much garbage as possible. Link in every MCP server under the sun, then make as many calls as you can using that thicc ass context window.

Add in redundant calls to the LLM server whereever possible.

For example, create git hooks to make LLM calls on pre-commit and pre-push. Then make those same calls in your CI/CD process. Make sure every new commit on a PR or feature branch causes every one of these to be re-run.

Every commit and CI workflow should trigger as many "tests" as possible. Some ideas:

• Vulnerability "scan"
• Changelog generator
• Commit description improvement
• Unit test generation
• Integration test generation
• Code style suggestions
• Update the docs
• Make a blog post describing the improvements this major/minor release.

For compounding effect, if you can manage it, stuff the output of every previous call into the context window of the next one to run.

To make sure you are credited with the usage, setup your editor to run an LSP that makes LLM calls whenever possible.

Run some on save, run some as a part of linting and static analysis checks, run some on every keystroke.

Make sure to stuff this crap in your editor's global config but only scoped to the paths associated with company projects. That way you get the increased token usage explicitly attributed to you without committing it to git and thus "sharing the credit" with all of your teammates. Still runs on the company projects without ruining your ability to quickly open random text files. Also, I would make sure to set a timeout on the LSP to prevent the AI nonsense from blocking real linters and tools, keeping your editor nice and responsive.