export * from './agent'  // L40

The AI SDK also includes a harness abstraction for using established agent harnesses such as Claude Code, Codex, and Pi through `HarnessAgent`.

The documentation advertises `HarnessAgent` as the public API for the harness abstraction, but the `packages/ai` index exports its agent surface via `export * from './agent'` with no `HarnessAgent` symbol visible in the provided API surface. A developer following the intro will attempt to `import { HarnessAgent } from 'ai'` and find no such export (or a differently named one), causing an import error or confusion about the correct symbol.

Either export `HarnessAgent` (or the actual harness class name) from `packages/ai/src/index.ts`/`./agent`, or update the introduction to reference the correct exported symbol (e.g. the real agent class name) and link to its API reference.

export * from './generate-text'  // L48

import { generateText } from "ai";

const { text } = await generateText({
  model: "anthropic/claude-sonnet-5.5",
  prompt: "What is love?",
});

The intro example passes a plain string as `model`. In the AI SDK, `generateText`'s `model` parameter historically requires a LanguageModel instance or gateway provider model (e.g. `gateway('anthropic/...')` or `anthropic('...')`), not a raw string. If string model IDs are not accepted by the current `generateText` signature, copying this snippet fails at runtime/type-check. The provided API surface does not show any string-accepting overload.

Verify whether `generateText` accepts string model IDs; if not, update the example to use `gateway('anthropic/claude-sonnet-5.5')` (with the `gateway` export shown at index.ts L5) or the provider factory, matching the actual `model` parameter type.

export { toolSearch } from './tool-search/tool-search'  // L58

(not documented)

`packages/ai` explicitly exports a top-level `toolSearch` API that receives a dedicated line in the index. The introduction page (the only doc provided) never mentions it, and no linked reference is visible in the scraped content, so developers scanning the docs would not know this export exists.

Add `toolSearch` to the API reference/index of documented exports, or remove it from the public surface if it is not intended to be public.

export * from './upload-skill'  // L65

(not documented)

`packages/ai` re-exports an entire `upload-skill` module (plus `upload-file` at L64, `rerank` at L55, `realtime` at L53, etc.), none of which the introduction page covers. The introduction does not enumerate the Core API surface, so these are omissions rather than contradictions, but `uploadSkill` in particular has no visible documentation reference in the provided material.

Ensure each wildcard-exported module (upload-file, upload-skill, rerank, transcribe, translate, rerank, realtime, tool-search, etc.) has corresponding API reference documentation, or note them as experimental in the docs.