What's next

The Beta covers the full taste loop: create a user, index linked content, compose, then search / rerank / ask / explain / clusters. A few things are built but not part of the supported Beta path yet. Here's the honest status so nothing surprises you.

Coming soon

Batch indexing

Today, POST /v1/index handles one item per call, synchronously. A batch endpoint (POST /v1/index/batch) for loading many items at once is in progress but not supported for the Beta; don't build on it yet. For now, loop over POST /v1/index (see the walkthrough).

Indexing performance

Indexing is synchronous per call, but the link writes that connect content to a user (and feed composition) settle a moment after POST /index returns. On slow or large catalogs this matters in two ways:

1. An early compose can miss content that hasn't finished indexing, so the taste profile is built from only part of a user's linked items.
2. compose can return 400 compose_no_children if you call it immediately after indexing.

What to do:

• Wait a few seconds (≈3 to 5s) after your last POST /index before calling compose.
• If a profile looks thin or incomplete, re-run compose once indexing has settled.
• rerank orders only the candidates you send, so it's unaffected by this latency.

A faster bulk-indexing path (batch) is part of resolving this; see Batch indexing above.

Where to go

• Run the working loop → Walkthrough
• Look up an endpoint → Operations
• Understand the model → Concepts