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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@iquly/sdk

v1.1.0

Published

Official SDK for IQuly AI Tools Platform

Readme

@iquly/sdk

Official TypeScript SDK for the IQuly AI Tools Platform.

Installation

# Using npm
npm install @iquly/sdk

# Using yarn
yarn add @iquly/sdk

# Using pnpm
pnpm add @iquly/sdk

# Using bun
bun add @iquly/sdk

Quick Start

import { IQuly } from "@iquly/sdk";

// Initialize the client
const client = new IQuly({
  apiKey: "your-api-key",
  // Optional configurations
  baseUrl: "https://iquly.com/api", // Default
  timeout: 30000, // Default: 30 seconds
});

// Get a toolkit
const toolkit = await client.getToolkit("toolkit-id", "provider");

// Execute a function
const result = await client.executeFunction("function-id", {
  // function parameters
});

// Listen to execution events
client.on("execution.complete", ({ functionId, result }) => {
  console.log(`Function ${functionId} completed:`, result);
});

client.on("execution.error", ({ functionId, error }) => {
  console.error(`Function ${functionId} failed:`, error);
});

Features

  • 🔒 Type-safe API with TypeScript support
  • 🚀 Promise-based async/await API
  • 📦 Built-in TypeScript types
  • 🎯 Event-driven architecture
  • ⚡ Automatic request timeout handling
  • 🔄 Vercel AI Tools compatibility

Configuration

The SDK accepts the following configuration options:

interface IQulyConfig {
  apiKey: string; // Required: Your IQuly API key
  baseUrl?: string; // Optional: API base URL (default: https://iquly.com/api)
  timeout?: number; // Optional: Request timeout in ms (default: 30000)
  retryAttempts?: number; // Optional: Number of retry attempts
  debug?: boolean; // Optional: Enable debug mode
}

Error Handling

The SDK provides several custom error types for better error handling:

  • IQulyError: Base error class for all SDK errors
  • AuthenticationError: Thrown when authentication fails
  • RateLimitError: Thrown when rate limit is exceeded
  • ToolExecutionError: Thrown when a tool execution fails
  • ValidationError: Thrown when input validation fails
try {
  await client.executeFunction("function-id", params);
} catch (error) {
  if (error instanceof AuthenticationError) {
    // Handle authentication error
  } else if (error instanceof RateLimitError) {
    // Handle rate limit error
  } else {
    // Handle other errors
  }
}

Events

The SDK emits the following events:

  • execution.complete: Emitted when a function execution completes successfully
  • execution.error: Emitted when a function execution fails