Introduction

What the AICE SDKs are, which services they cover, and the two ideas every integration rests on.

AICE is a set of independent services: an agent runtime, a recommendation engine, document search, a crawler, a data connector, KYC checks and a code sandbox. Each one exposes a REST API. The SDKs wrap those APIs in typed clients for Python and TypeScript that share one transport, so retries, errors and authentication behave the same way whichever service you call.

Two ideas to hold on to

Services

ServiceWhat it doesPythonTypeScript
Agent PlatformStreaming conversational agents with tools, memory and human approvalaice-agent-platform@aiceafrica/agent-platform
RecommendationTrack interactions, train a model, get ranked recommendationsaice-recommendation@aiceafrica/recommendation
KnowledgeDocument ingestion, scopes and semantic searchaice-knowledge@aiceafrica/knowledge
CrawlerBudgeted web crawls, reviewed then published to Knowledgeaice-crawler@aiceafrica/crawler
Data BrainQuery connected data sources without exposing credentialsaice-data-brain@aiceafrica/data-brain
KYCDocument analysis, face capture and verificationaice-kyc@aiceafrica/kyc
SandboxIsolated sessions for running codeaice-sandboxnot yet

Want every client behind one object? The umbrella SDK (aice-sdk / @aiceafrica/sdk) builds each one lazily from a single project key.

How the pieces fit

browser ──▶ your backend ──(project key + X-User-Id)──▶ AICE service

The SDKs are server-side clients. The project key is a credential for everything in that project, so it lives in your backend's environment, never in a browser bundle or a mobile app. A browser that needs an AICE feature, such as a chat window, calls your backend, and your backend calls AICE. The chat UI guide shows that pattern end to end.

Where to start

On this page