The Qipit Mobile Copy API moves digital cameras and camera phones beyond just taking pictures by enabling developers to use the camera sensor to create “scan quality” highly legible, printable, ink-on-white digital copies of anything written or printed.
The technology enables developers to create a variety of applications and services ranging from logistics applications to track inventories in unconventional place, sales force automation applications to get forms and signed contracts back to headquarters and for e-tailers (and e-card services) to enable customers to add the personal touch of their own handwriting for gift cards. Other potential uses include applications and mash-ups with social networking sites to share class notes or other written information.
How it works
You submit a JPEG photo of anything written or printed, such as a document, note or receipt to the Qipit scanning engine. The technology transforms this picture into a crisp clear ink-on-white copy (in the form of a JPEG). The Qipit scanning engine automatically corrects for framing (crops it), compression, noise, vignetting, illumination, glare, contrast, tilt, and skew as well as motion and optical blur.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org
So far, we don't have a record of any changes to this API