Audream provides a standard Agent Skill, a remote MCP server, a cross-platform CLI, and a REST/OpenAPI contract. Choose the narrowest interface that fits the workflow: MCP for interactive agents, the CLI for local files and automation, and REST for application integrations.

Agent entry points

Agent Skill

Install reusable Audream workflow and safety instructions in an Agent Skills-compatible host.

Remote MCP

Connect an agent with OAuth 2.1 and expose scoped Audream tools without copying an API key.

Audream CLI

Upload local audio, poll processing jobs, query Notes, and generate artifacts from scripts.

OpenAPI specification

Import the complete tool contract, request schemas, and response schemas.

LLM index

Discover the most important human-readable and machine-readable resources.

Complete agent context

Load all Audream guides as a single text document for retrieval or coding agents.

Ask across notes

Answer questions from processed notes and return the supporting note IDs.

Install the Agent Skill

The complete skill directory is public at:
Machine-readable entry points:
Install the skills/audream directory in an Agent Skills-compatible host. The skill selects MCP, CLI, or REST based on the task and loads detailed references only when needed.

Connect the remote MCP server

Use this Streamable HTTP URL:
Audream publishes OAuth authorization-server and protected-resource metadata. Compatible MCP clients discover OAuth automatically, open Audream Web for account authorization, use authorization code with PKCE, and receive a resource-bound access token. Default authorization grants read and processing access. Additional scopes are requested when the client needs them: The MCP server exposes Note discovery, retrieval, workspace Ask, updates, Insights, artifacts, and confirmed deletion. Local audio upload is intentionally excluded because passing large audio as base64 through model context is inefficient and unsafe; use the CLI for local files.

Install the CLI

The CLI requires Node.js 20 or newer and has no runtime package dependencies:
It emits JSON to stdout and diagnostics to stderr. Permanent deletion commands require an exact --confirm NOTE_ID value.

Import the OpenAPI contract

Use this URL when an agent platform accepts an OpenAPI document:
For direct REST tools, configure bearer authentication with an Audream API key stored in the agent runtime’s secret manager:
The OpenAPI operationId values are stable tool identifiers. Prefer them over generating names from URL paths. Do not expose every mutation to an autonomous agent by default. Start with the smallest tool set required by the workflow.
Require explicit user confirmation immediately before deleteTranscription or deleteNote. Do not treat an earlier general request as deletion approval.

Define a compact Ask tool

Agents that only need knowledge retrieval can expose a single tool instead of the complete API:
The tool executor calls POST /v1/ask and returns the API response without discarding citations:
Preserve the returned note_ids in the final answer so the user can inspect the source notes.

Handle asynchronous tools

Transcription, Insights, and artifact generation can return 202 Accepted. A tool executor must keep the job state outside the language model and poll the corresponding GET operation.
  1. Return a durable note_id from the initial tool call.
  2. Poll at intervals of at least 2 seconds.
  3. Stop on 200 or a documented terminal error.
  4. Apply a bounded deadline and exponential backoff for transient failures.
  5. Never let the agent interpret 202 as a completed result.
See Processing status for response handling and idempotency rules.

Agent execution policy

Use these rules in the agent’s system instructions or tool middleware:

Context and privacy

  • Keep the API key and Audream responses in a trusted server-side agent runtime.
  • Send only the note content needed for the current task to any additional model provider.
  • Prefer askWorkspace when the agent needs an answer rather than complete transcripts.
  • Do not log bearer headers, raw audio, transcripts, or generated artifacts by default.
  • Rotate the key immediately if it appears in a prompt, trace, repository, or client bundle.
Remote MCP tokens are audience-bound to the Audream MCP resource and must not be forwarded to REST endpoints or other services. REST API keys remain the appropriate credential for the CLI and server-side application integrations.