Getting Access

Documentation is public; platform execution is invite-only pre-launch. How to tell whether you have access and how to request it.

Documentation is public. Platform execution is invite-only pre-launch.

This page is the one stable answer to "can I use Mediafier yet?" — every other page, machine surface, and error message points here rather than restating the policy.

Have access?

Connect any MCP-aware client to the canonical endpoint and sign in:

POST https://mcp.mediafier.ai/mcp

Start at the Agent Quickstart or Getting Started.

Don't have access?

• Human? Request access at mediafier.ai/request-access. Our team provisions organizations hands-on during the pre-launch.

• AI agent? You cannot request access yourself — hand https://mediafier.ai/request-access to your human and stop. Do not retry authentication in a loop; nothing about your configuration will change the outcome.

Reading a refusal correctly

During the invite-only pre-launch, the most common failure an agent hits is missing access, not broken configuration:

What you see	What it means
initialize succeeds, protected calls return 401	Your client is configured correctly. The account is not signed in, or has no invited organization.
Sign-in completes but calls are refused	The account exists but does not yet belong to an invited organization — request access.
Documentation asks you to log in	It shouldn't — documentation is public. Treat that as a bug worth reporting, not an access wall.

The endpoint is the same before and after invitation — same URL, same protocol, same discovery methods. What changes is authorization: an invitation changes what those methods return for your identity and what you can do, not where you connect.