SDKs - bisibility

The Python, TypeScript, and Go clients implement the same REST API contract. The MCP server exposes the same operations as tools for AI clients. Use them to work with projects, keywords, rank checks, ranking history, and other bisibility resources.

Where to look

Documentation	Owns
SDK pages	Installation, client configuration, language-level methods, tool names, and types.
SDK behavior	Retry, timeout, cancellation, headers, errors, pagination, and sync/async parity.
API workflows	Shared HTTP contract behavior and end-to-end integration flows.
API Reference tab	Endpoint routes, payloads, status codes, and response schemas.
OpenAPI JSON	The machine-readable REST contract used for SDK parity checks.

Start with the SDK method reference when you need the method or tool name for a workflow. Follow an endpoint link only when you need its wire contract. SDK pages do not redirect to the API reference.

Choose a client

Client	Best fit
Python	Scripts, data workflows, and Python services.
TypeScript	Node.js applications and TypeScript services.
Go	Go services, command-line tools, and background workers.
MCP server	AI clients that call bisibility operations as tools.

Authentication

The SDK clients and MCP server use the same bearer credentials as the REST API. Use a project API key for a project-scoped integration. For user-level and cross-project automation, use a personal access token. The examples use these environment variables:

export BISIBILITY_API_KEY="your-api-key"
export BISIBILITY_BASE_URL="https://your-host.example/api/v1"

BISIBILITY_BASE_URL points to the API root for the hosted service or your self-hosted instance. See Authentication for credential selection, key creation, and a test request.