NatLabRockies / NatLabRockies/COMPASS
Store results from paid API searches
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 4
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 17
Description
If users apply paid API searches like Tavily or Serper, we should cache the query results locally somehow (or maybe even centrally?) so that they don't have to pay for repeated searches. The cache can be invalidated after some time, which can also be controlled by the user.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the Tavily and Serper search integrations, then clarify whether caching is local or central and how users control expiration. Done means repeated paid searches reuse stored results and expiration behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100