hyScore|brandrisk helps to identify critical content on journalistic websites, which are not optimally suited as an environment for an advertising campaign. The hyScore|brandrisk indicator identifies e.g. reports on catastrophes, accidents, and crimes. This provides you with an optimal basis for making decisions on the delivery of advertising within these environments, in order to prevent unwanted placements in advance.
This documentation is for the hyScore|brandrisk API.
hyScore|brandrisk is a hyScore analysis method that displays a unique indicator ("0" or "1") for a single URL or text in the output/result of the hyScore|analyze interface used for a text/article/content classified as critical.
The BrandRisk functionality is optional and can be output as additional information (add-on) within the previous analysis results of the hyScore|analyze interface.
hyScore|brandrisk is available via...
- AWS Marketplace
- in combination with hyScore|analyze
- or as stand-alone Endpoint
- German (DE)
- English (EN)
More information available at https://hyscore.io.
How can I get an API-Key?
Just sign-up for our hyScore|cockpit and a personal API-Key will be created automatically. As an alternative, you can write us an email to email@example.com. We offer 1.000 API requests per month for free so that you can test our service without any costs or risks.
Most of our customers' use cases can be divided into two different scenarios: real-time and bulk processing. For both the integration is exactly the same, what differs is how the data is "collected" and used.
Wanting to categorize and catalog your website inventory, is an example of batch processing. You might send us several thousand or even millions of URLs. As this will take some time to process and analyze, let's say you "come back" 15 minutes later to pick up the results. The nice thing is that picking up the results is just sending us the same request again. This keeps the implementation effort for the integration very low.