For the complete documentation index, see llms.txt. This page is also available as Markdown.

Releases & Deprecation

How Mediafier ships change, what deprecated means for a tool or surface, and where an agent learns about it first.

The live response is the contract; documentation is the policy. An agent learns that something changed from authenticated discovery and from the structured response to a call — never by re-reading cached docs.

How change reaches you

  • Authenticated discovery is the authority. tools/list and resources/list return the current names, schemas, and activation state for your organization. An agent that discovers before calling sees a change the moment it ships.

  • Structured responses carry the notice. A deprecated tool or surface answers with a structured error that names the replacement and the relevant dates, together with the trace identifier, so an agent can re-plan rather than guess.

  • Documentation states the policy, not the calendar. Pages carry a last_verified date; Compatibility dates every client claim. Neither replaces the live response.

What "deprecated" means

Term
What it means for you

Available

Callable now for organizations that have it enabled; the authenticated product is the authority.

Early access

Available to invited organizations; controls and features may change between checks.

Deprecated

Still callable; a replacement exists and is named in the response. Plan the move.

Retired

No longer callable; the structured refusal names the replacement.

Deprecation and retirement of a governed capability are announced through the same governed endpoint that serves it. The notice period for a specific deprecation is stated with that deprecation — in the response and in your organization's agreement — rather than assumed from this page.

What does not change without notice

  • The canonical endpoint, POST https://mcp.mediafier.ai/mcp.

  • The authentication model: access tokens as bearers; Agent Credentials exchanged, never presented directly.

  • The guarantees on every governed call: organization-scoped, authenticated and authorized before execution, metered where applicable, audited on allowed and refused calls, trace-correlated, fail-closed.

What this page is not

  • It is not a changelog. Changes to how the endpoint behaves that an integration may need to act on are recorded, dated by production, in Protocol Changes; this page is the standing policy behind them.

  • It is not a per-capability status board. Availability is stated at the page level in these docs; the authenticated product is the authority for what your organization can call today.

Where to go next

If you're…
Read next

Handling a refused or deprecated call

Checking a client before you depend on it

Checking what changed on the endpoint

Discovering what you can call right now

Last updated