In general, there are two ways of how you can use the hyScore.io API. Depending on your specific use-case it might be ok to aim for a batch processing approach instead of requesting the API in real-time.
How we define "live processing" (real-time).
Depending on your use case we define "real-time" as a process where you request the API permanently and expect a JSON response within ~50-250ms.
Example: the personalization use case is a real-time case. In this case, you want to enrich e.g. user profiles with contextual information. This means you want to know what the user is currently reading and what he is interested in overtime. With this kind of information, you are able to personalize content on your website for this specific user, offer him specific products or personalized advertising.
How we define "batch processing".
As "batch processing" we understand a huge amount of URLs that will be sent once towards the API for a one-time analysis which is not time critical.
Example: You have 1 million URLs you want to analyze and classify. With the first requests, you send every single URL. You wait e.g. 15 minutes and with a second request, you collect the results.
Depending on your use case and individual request behavior we discuss which processing is the most efficient for you.