feat: Add Heurist API Integration as New Model Provider #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to:
Risks
Low - This change adds a new model provider integration (Heurist) with proper API key handling and follows existing patterns for model providers.
Background
What is Heurist?
Heurist is a DePIN (Decentralized Physical Infrastructure Network) protocol for AI inference that:
Aggregates compute resources from GPU owners and data centers to provide cost-effective API access to open source models
Reduces costs by 60-95% compared to closed source alternatives
Has processed over 1 billion AI inference requests
Has 11k unique addresses contributing GPUs since April 2024
Powers multiple production applications including:
Partners with key infrastructure providers like Aethir, Exabits, Spheron, Gateway Network
What does this PR do?
This PR adds support for the Heurist API as a new model provider. Specifically:
The integration allows us to leverage Heurist's cost-effective infrastructure for accessing open source LLMs while maintaining our existing architecture patterns.
What kind of change is this?
Features (non-breaking change which adds functionality)
Documentation changes needed?
My changes require a change to the project documentation to document:
Testing
Where should a reviewer start?
Detailed testing steps
pnpm start
Screenshots
N/A - Backend API integration changes only
Deploy Notes