Semantic chunking splits documents at inferred topic boundaries rather than fixed token counts. It can produce useful retrieval chunks for unstructured content such as transcripts and email threads, but adds embedding cost during ingestion. section 5.3.5
To find boundaries:
- Embed each sentence in the document. section 5.3.5
- Compare embeddings of consecutive sentences. section 5.3.5
- Start a new chunk where similarity drops sharply. section 5.3.5
The choice is an index-level configuration. Recursive splitting is the platform default for broadly varied content; structure-aware chunking is an alternative for well-structured documents. Fixed-token cuts can split sentences or code blocks in policy and engineering documents. section 5.3.5 section 10.5
Listing 10.8 Populating the knowledge base
# Ingest company documents (typically done as a setup step or scheduled job)
platform.data.create_index(
name="company-knowledge",
embedding_model="text-embedding-3-small",
chunking_strategy="semantic", #A
metadata_schema={"department": "string", "doc_type": "string"})
# Batch ingest documents
for doc_path in company_docs:
platform.data.ingest(
index_name="company-knowledge",
document_id=doc_path.stem,
file_path=doc_path,
metadata={"department": "engineering", "doc_type": "policy"})Configure semantic chunking when creating a company knowledge index, then ingest documents with metadata. section 10.5
Once populated, the index supports retrieval that grounds answers in organizational knowledge. The additional ingestion cost buys topic-sensitive boundaries, not a guarantee that every numbered clause or code block remains intact. section 10.5 section 5.3.5

