npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@innodatalabs/ilabs-api

v1.0.2

Published

iLabs API client

Downloads

5

Readme

ilabs-api-js

NodeJS client for InnodataLabs prediction microservices.

Installation

npm i @innodatalabs/ilabs-api

Example

const Client = require('@innodatalabs/ilabs-api');

const userKey = ...;  // this is your secret API access key
const domain = ...;   // prediction domain to use

const client = new Client({userKey});

async function predict(domain, content) {
    const result = await client.call(domain, content);
    return result.toString();
}

predict(domain, 'Some input text (or file, or Buffer)').then(console.log).catch(console.error);

API

Concepts

InnodataLabs prediction microservices are RESTful services. Each service takes one binary string (e.g. NodeJS Buffer object), and returns binary string (another NodeJS Buffer object). Input/output types are typically UTF-8 encoded strings, but please consult the documentation of the particular prediction domain for the explanation of input/output format.

InnodataLabs RESTful endpoint lives at https://ilabs-api.innodata.com/v1. This endpoints hosts multiple services. A string that we call prediction domain identifies concrete service.

Client

Constructor arguments:

  • userKey - required to access the API
  • endpoint - (optional) can be used to switch to the alternative endpoint (staging, testing)
  • userAgent - (optional) user agent string to send to the endpoint

async Client.call(domain, content)

Asynchronous method that does the prediction.

Arguments:

  • domain - prediction domain (required)
  • content - the content. Can be one of:
    • string - will be encoded with UTF-8
    • NodeJS Buffer object - its content will be sent to the endpoint
    • NodeJS Stream - stream content will be piped into the remote endpoint

Returns:

NodeJS Buffer object