What's next

The Beta covers the full taste loop: create a user, create content entities, link them, 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 content creation

Today, POST /v1/entity with content handles one item per call, synchronously. A batch endpoint (POST /v1/entity/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/entity with content (see the walkthrough).

Link-settlement performance

Creating a content entity is synchronous per call, but the link writes that connect content to a user and mean-pool the parent settle a moment after POST /v1/entity with content returns. On slow or large catalogs this matters in two ways:

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

What to do:

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

A faster batch content-creation path is part of resolving this; see Batch content creation above.

Where to go

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