Identity is personal.

We think authentication should be be courteous, personalised, and never a hassle.

Quill is a REST API providing bio-device authentication. It works on any browser, requires no hardware and integration is simple.

Easy Integration.

The first thing you need is a valid API user_id & corresponding secret and you get these when you create an account.

Opening the account grants you access to the Quill plugin and you are now free to activate any html pages you wish, simply by adding the js snippet:

[YOUR ORIGINAL HTML]
<script src="path/to/Quill.js"></script>

What does Quill do?

Quill trains itself by gathering a small number of activations emitted by user operations on the device, and then pairs that user behaviour with the device, tagging it as "normal". Subsequent activations by any user on the device are then distance scored, with Quill providing a confidence rating as to whether the device is being operated by the same user or not.

Invisible Onboarding.

As part of Quill's training phase your users' authentication behaviour and devices usage are all mapped to create comprehensive user profiles without inconveniencing them in any way.

Multiple Devices.

Multiple devices - these just get enrolled automatically as part of the invisible onboarding; users can also actively add new devices as they choose.

Variable Authentication.

Your behaviour changes depending upon the device you use. No problem, Quill automatically handles this. Changes through time are handled similarly.

Adaptive Authentication.

Quill can be set up in one of 3 different modes, Quiet, Silent or Noisy, to allow for differing levels of continuous authentication.

REST & cURL

The Quill detection API works via a RESTful interface, and the API lives on this domain.

All requests are performed issuing standard HTTPS GET requests to variants of this endpoint using your unique account keys. So, for example, here's how you might issue a request with cURL -

curl -i "https://quillapi2.herokuapp.com/quillapi2/v0.0.13/api_user=APU/api_secret=APS/..."

And the results returned are generally consumed in one of two ways -

200 OK {json data pack}
400 Bad Request {'error': 'Bad request'}

Finding Out More

To find out more about how Quill works, sign up for an account and learn the various API requests and responses, go to our api for more.