> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/transfer-media-encode-and-publish/understand-how-local-media-reaches-podigee.md).

# Understand how local media reaches Podigee

Understand the split between MCP control messages and direct media transfer.

Media bytes do not travel through an MCP conversation. Podigee uses MCP for upload control and a direct HTTPS `PUT` for the file itself.

## Choose a client

| Starting point                                                       | Suitable client                                             |
| -------------------------------------------------------------------- | ----------------------------------------------------------- |
| A local audio or video file                                          | The pdg CLI, or another client that can send an HTTPS `PUT` |
| Metadata, analytics, imports, listeners, or media already in Podigee | A compatible hosted remote MCP client                       |

The pdg CLI creates an upload session, transfers the file directly, completes the session, and returns an opaque `upload_id`. A publishing request attaches that upload with `{ "source": "upload", "upload_id": "..." }`.

## Hosted connector boundary

A hosted chat connector cannot upload an arbitrary file from your computer. Use the pdg CLI to bring new media into Podigee, then use either client to manage the uploaded or encoded result.

Podigee does not fetch episode media from a remote URL on an agent's behalf.

## Security boundary

Signed upload URLs are short-lived capabilities. Do not paste them into chat, logs, tickets, or documentation. The public `upload_id` is the stable reference for later Podigee calls.

## Related tasks

* [Upload local media with the pdg CLI](/documentation/start-here/ai-agents/transfer-media-encode-and-publish/upload-local-media-with-the-pdg-cli.md)
* [Upload local media with an HTTP client](/documentation/start-here/ai-agents/transfer-media-encode-and-publish/upload-local-media-with-an-http-client.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/transfer-media-encode-and-publish/understand-how-local-media-reaches-podigee.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.