Hi Boris, yes, I’m a real person — sorry if my first message sounded too formal or automated.
English is not my first language, so I use translation tools and AI assistance to write in English. Sorry if the wording came across strangely.
ManaPilot is a small independent Italian Hearthstone coaching and deck-analysis project I’m building.
The goal is to help players better understand their deck, archetype, matchups and the current meta, with proper attribution to the sources used.
I’m not asking for a private API, and I don’t want to bypass anything or use your data in a way you don’t allow.
What I’m mainly interested in is limited aggregate/meta information, such as archetypes, classes, rank brackets, patch/report period, sample size or games played, winrate, popularity and matchup winrate, only when those values are publicly visible and only if you allow it.
I’m not asking for user-level data, private datasets, raw replay data, paid/restricted data, or anything behind login/paywalls.
Ideally, I would like to store selected public aggregate fields in a staging database for validation, with clear HSGuru attribution and links back to the original HSGuru pages whenever the data is used.
Attribution and source links are completely fine for me. Actually, I think that is the correct way to do it. If data comes from multiple sources, I can show links/attribution for each source used.
The preferred approach would be low-frequency automated access, for example checking for relevant meta updates about once per week, or following any stricter rate limit you prefer. I don’t need hundreds of requests per day.
If automated access is not allowed, that’s completely fine — I’ll respect that. In that case, I’d like to understand whether manual use, source links, attribution-only use, or any other limited usage would be acceptable.
The project is still in early development, so the repository is currently private while I finish and clean up the core system.
I’d be happy to follow any rate limits, attribution requirements, retention limits, takedown requests, or other rules you prefer.
And if there’s ever a way to collaborate more properly around this kind of use case, I’d be very open to that too.
Hi Boris, yes, I’m a real person — sorry if my first message sounded too formal or automated.
English is not my first language, so I use translation tools and AI assistance to write in English. Sorry if the wording came across strangely.
ManaPilot is a small independent Italian Hearthstone coaching and deck-analysis project I’m building.
The goal is to help players better understand their deck, archetype, matchups and the current meta, with proper attribution to the sources used.
I’m not asking for a private API, and I don’t want to bypass anything or use your data in a way you don’t allow.
What I’m mainly interested in is limited aggregate/meta information, such as archetypes, classes, rank brackets, patch/report period, sample size or games played, winrate, popularity and matchup winrate, only when those values are publicly visible and only if you allow it.
I’m not asking for user-level data, private datasets, raw replay data, paid/restricted data, or anything behind login/paywalls.
Ideally, I would like to store selected public aggregate fields in a staging database for validation, with clear HSGuru attribution and links back to the original HSGuru pages whenever the data is used.
Attribution and source links are completely fine for me. Actually, I think that is the correct way to do it. If data comes from multiple sources, I can show links/attribution for each source used.
The preferred approach would be low-frequency automated access, for example checking for relevant meta updates about once per week, or following any stricter rate limit you prefer. I don’t need hundreds of requests per day.
If automated access is not allowed, that’s completely fine — I’ll respect that. In that case, I’d like to understand whether manual use, source links, attribution-only use, or any other limited usage would be acceptable.
The project is still in early development, so the repository is currently private while I finish and clean up the core system.
I’d be happy to follow any rate limits, attribution requirements, retention limits, takedown requests, or other rules you prefer.
And if there’s ever a way to collaborate more properly around this kind of use case, I’d be very open to that too.