You May Be Interested in these APIs
IIIF Image API Search Results & Alternatives
SYSTRAN.io platform is a collection of APIs for Translation, Multilingual Dictionary lookups, Natural Language Processing (Entity recognition, Morphological analysis, Part of Speech tagging, Language Identification...) and Text Extraction (from documents, audio files or images).
Free Search API with 1 million free queries per month. Web Search More than 2 billion pages indexed. English, German and Chinese results. Sorted by relevancy. News Search News articles from newspapers, magazines and blogs. Sorted by publishing date, with author and article image. Trending News Trending news, grouped by topic. Topics sorted by buzz (number of sources reporting on same topic). One main article per topic + related links. Trending Topics Trending news, grouped by topic. Topics sorted by buzz (number of sources reporting on same topic). All full articles per topic, sorted by publishing time. Suggestions Suggestions with auto completes for query substrings and corrections for misspelled terms.
FaceRect is a powerful and free API for face detection. It finds faces (both frontal and profile) on the image specified by URL or uploaded as a file and is able to find multiple faces on a single photo, producing JSON output with a bounding box for each face found. Check out visual demo here: http://apicloud.me/apis/facerect/demo/. Note that additionally FaceRect can find face features for each detected face (eyes, nose and mouth). For more precise face feature detection please see our FaceMark API: https://www.mashape.com/apicloud/facemark
IMG4Me is a free service to convert your text into image. You can use this service to prevent crawlers and robots from copying your email address, articles, or website contents. Meanwhile, you can handle encoding errors as well if your text is in non-English characters.
Related APIs in Category: Images
The International Image Interoperability Framework (IIIF) defines several application programming interfaces that provide a standardised method of describing and delivering images over the web, as well as "presentation based metadata"(that is, structural metadata) about structured sequences of images. If institutions holding artworks, books, newspapers, manuscripts, maps, scrolls, single sheet collections, and archival materials provide IIIF endpoints for their content, any IIIF-compliant viewer or application can consume and display both the images and their structural and presentation metadata. There are many digitisation programmes that have resulted in a particular collection’s content exposed on the web in a particular viewer application, but these various collections have not typically been interoperable with one another, and end users or institutions cannot substitute a viewer of their choice to consume the digitised material. The IIIF aims to cultivate shared technologies for both client and server to enable interoperability across repositories, and to foster a market in compatible servers and viewing applications. The IIIF Image API specifies a web service that returns an image in response to a standard HTTP or HTTPS request. The IIIF Presentation API specifies a web service that returns JSON-LD structured documents that together describe the structure and layout of a digitized object or other collection of images and related content. Version 1.0 of the Presentation API was published in 2013 and of the Search API in 2016.
IIIF Website Summary:
This document describes an image delivery API proposed by the International Image Interoperability Framework (IIIF) group. The IIIF Image API specifies a web service that returns an image in response to a standard HTTP or HTTPS request. [...] It could be adopted by any image repository or service, and can be used to retrieve static images in response to a properly constructed URI. Please send feedback to [email protected] This document is intended for architects and developers building applications that share and consume digital images, particularly from cultural heritage institutions, museums, libraries and archives. [...] It is recommended that the response be a 303 status redirection to the Image Information document’s URI. Implementations may also exhibit other behavior for the base URI beyond the scope of this specification in response to HTTP request headers and methods.