> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SDK overview

> Zespan ships a TypeScript SDK and a Python SDK with the same feature set. This page maps what each one does and where to go for a specific feature, instead of one giant per-language reference.

Zespan has two official SDKs — **`@zespan/sdk`** for TypeScript/Node and **`zespan`** for Python — built on the same core: auto-instrumentation for your LLM provider of choice, manual span tracing for anything else, and clients for prompts, datasets, and guardrails. Neither language is the "primary" one; both get the same features on the same release cadence.

Most feature pages below cover **both languages on one page**, with TypeScript and Python usage side by side — you only need the language-specific reference pages (below) for full installation, configuration, and initialization details.

## Language references

<CardGroup cols={2}>
  <Card title="TypeScript SDK" icon="square-code" href="/sdk/typescript">
    Install, initialize, and configure `@zespan/sdk` — provider auto-patching, agent workflows, serverless flush handling.
  </Card>

  <Card title="Python SDK" icon="terminal" href="/sdk/python">
    Install, initialize, and configure `zespan` — provider auto-patching, agent workflows, serverless flush handling.
  </Card>
</CardGroup>

## By feature

| Feature                                                   | Page                                          | Languages                             |
| --------------------------------------------------------- | --------------------------------------------- | ------------------------------------- |
| Manual span tracing (RAG, custom ops)                     | [Manual spans](/sdk/manual-spans)             | TypeScript + Python                   |
| Multi-agent workflows, handoffs                           | [Agent tracing](/sdk/agent-tracing)           | TypeScript + Python                   |
| Prompt fetch/compile/versioning                           | [Prompt management](/sdk/prompt-management)   | TypeScript + Python                   |
| CI quality gate                                           | [CI/CD (zespan-gate)](/sdk/cli)               | CLI, language-agnostic                |
| Content checks (block/redact/flag)                        | [Guardrails](/sdk/guardrails)                 | TypeScript + Python                   |
| Running a pipeline over a dataset                         | [Dataset runs](/sdk/dataset-runs)             | TypeScript + Python                   |
| FastAPI request tracing                                   | [FastAPI middleware](/sdk/fastapi-middleware) | Python only                           |
| Flask request tracing                                     | [Flask middleware](/sdk/flask-middleware)     | Python only                           |
| PII redaction                                             | [PII redaction](/sdk/pii-redaction)           | TypeScript + Python                   |
| Live SDK config updates, no redeploy                      | [Config propagation](/sdk/config-propagation) | TypeScript + Python                   |
| Bring your own OTel backend                               | [OTel integration](/sdk/otel-integration)     | TypeScript + Python                   |
| LLM provider / framework / vector DB auto-instrumentation | [Integrations](/sdk/integrations/overview)    | TypeScript + Python (per-integration) |

## Which page do I actually need?

* **Setting up tracing for the first time?** Start with the [Quickstart](/quickstart), then the language reference above for your stack.
* **Already tracing LLM calls, want to add something specific** — agents, prompts, guardrails, a dataset run? Go straight to that feature's page in the table above; each one has both languages in tabs, so you don't need the full language reference for it.
* **Using LangChain, Bedrock, Pinecone, or another named library?** That's [Integrations](/sdk/integrations/overview), not this page — auto-instrumentation is organized by vendor there, not by Zespan feature.