Get helicone costs

[waynehamadi]

Background

Changes

PR Quality Checklist

• I have run the following commands against my code to ensure it passes our linters:

  black . --exclude test.py
  isort .
  mypy .
  autoflake --remove-all-unused-imports --recursive --ignore-init-module-imports --ignore-pass-after-docstring --in-place agbenchmark

[github-actions]

PR Analysis

• 🎯 Main theme: Adding functionality to fetch costs from Helicone API and include it in the reports
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, the PR is focused as it introduces a new feature to fetch costs from an API and includes this data in the reports. All changes in the PR are relevant to this feature.
• 🔒 Security concerns: No, the PR does not introduce any obvious security concerns. The API key is fetched from the environment variables which is a good practice. However, it's important to ensure that this key is securely stored and not exposed in any logs or error messages.

PR Feedback

• 💡 General PR suggestions: The PR is generally well-structured and follows good practices. However, it would be beneficial to add tests to ensure the new functionality works as expected. Additionally, it would be good to handle potential exceptions that could be raised when making the API request.

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', just add -config_path=. For example: '/review --pr_reviewer.extra_instructions="focus on the file: ..."'