Search1API Ecosystem: Our Open Source Projects

One API, several ways to integrate

Search1API is one web access layer, but there is no single best client for every workload. Application code needs language-native types and errors. Coding agents work well with a CLI and reusable instructions. MCP clients should be able to connect without a custom integration.

The official open-source ecosystem now covers each of those paths, all backed by the same public API contract.

Official TypeScript SDK

Install the TypeScript client with:

npm install @search1api/client

The SDK provides typed requests and responses, structured error classes, safe retries for transient failures, configurable timeouts, batch operations, and DeepCrawl polling. It supports Node.js 18+ and other runtimes with a standards-compatible fetch implementation.

Source: superagents-lab/search1api-js

Official Python SDK

Install the Python client with:

pip install search1api

Python applications can use either the synchronous Search1API client or the asynchronous AsyncSearch1API client. Both expose the same public API coverage, error handling, retry policy, batch operations, and DeepCrawl helpers.

Source: superagents-lab/search1api-python

CLI and Agent Skill

The Search1API CLI, available as the short command s1, is designed for terminal workflows and coding agents:

curl -fsSL https://cli.search1api.com/install.sh | bash
s1 login

s1 login opens the OAuth 2.1 authorization flow in the browser. Existing API keys remain supported for scripts and CI.

Agents that support reusable skills can install the canonical Search1API skill:

npx skills add superagents-lab/search1api-cli

Source: superagents-lab/search1api-cli

MCP server

OAuth-aware MCP clients can connect directly to:

https://mcp.search1api.com/mcp

The hosted server exposes search, news, crawl, sitemap, and trending tools. Clients without OAuth discovery can continue using an API key, and local stdio integrations can run the npm package with npx.

Source: superagents-lab/search1api-mcp

Public OpenAPI contract

The TypeScript and Python SDKs are checked against Search1API's public OpenAPI contract. The same schema is available for teams that want to generate a client in another language or import the API into tools such as Postman and Insomnia.

View the public OpenAPI specification .

Which integration should you choose?

Building a TypeScript or Python application? Start with the official SDK for language-native configuration, errors, retries, batches, and polling.

Giving a coding agent terminal access? Use the CLI and Agent Skill.

Connecting an MCP-compatible AI client? Use the hosted MCP endpoint.

Using another language or a custom platform? Call the REST API directly or generate a client from the OpenAPI schema.

All four paths use the same Search1API account, credits, billing, and API capabilities. Choose the interface that fits the environment rather than building around a transport you do not need.

Contributing

The official SDK, CLI, and MCP repositories are maintained under the superagents-lab GitHub organization. Bug reports, focused feature requests, documentation fixes, and pull requests are welcome in the relevant repository.

---

Choose the right Search1API integration for your stack: Explore the SDK, CLI, MCP, and OpenAPI guides →