The API access is managed by the my.redlink.io dashboard. There you can create applications and generate keys for accessing the API.
OAuth2 is not supported at the moment, but it's something we've thought about. We'll add it as soon we have enough uses cases that justify its addition.
When you release a dataset, it will become available as component in your analysis chains. That means you can use your custom dataset to perform analysis operations (e.g., NER over those entities). It requires the dataset uses one of the supported schemas (SKOS, DC, FOAF or RDFS). Datasets can be released for your private usage only, or for the public marketplace, so other users can use it in their analysis chains.
Such kind of configurations are done from my.redlink.io dashboard:
When you publish a dataset, by default it will become publicly available under the following URI's schema:
If your URIs do not fit with such base URI, you can still access the data by using:
Custom domains will be available under a different cost model. Please, contact us at firstname.lastname@example.org for setting it up.
Through our data hub data.redlink.io we're pubicly offering raw Linked Data support. But SPARQL is restricted to the API.
That's because we are very chary with the quality of our service, and we want to deliver the best possible quality to our customers. Thus, taking into account the inherited complexity of SPARQL, we are not thinking to provide public SPARQL access to your datasets for now.