YouTube: 6 reads, 4 writes and 1 destructive call, one client

Channels, videos and uploads. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What YouTube can do here

The integration exposes 6 reads, 4 writes and 1 destructive call, each with a declared input and output schema rather than a page of documentation you would have to translate. Channels, videos and uploads.

How it authenticates

YouTube uses OAuth, so you link the account once and we hold the refresh token rather than a key you have to paste. The link is the credential: revoke it at YouTube and the calls stop here too, immediately, without anyone deleting anything on our side.

Called by name, not by capability

YouTube does not currently map onto a vendor-neutral capability, so you call its operations by name. That is the right shape when you genuinely mean this provider — which, for a service with its own model of the world, is most of the time.

• listChannels — read: Your own channels, with their statistics.
• listVideos — read: Videos by id, or the most popular in a region.
• searchMyVideos — read: Search within your own uploads, newest first.
• updateVideo — write: Update a video’s title, description, tags or privacy.
• deleteVideo — destructive: Delete one of your videos. This cannot be undone.
• uploadVideo — write: Upload a video file and publish it to your channel.
• listPlaylists — read: Your playlists.
• listPlaylistItems — read: The videos in one playlist.
• addToPlaylist — write: Add a video to one of your playlists.
• listComments — read: Comment threads on one of your videos.
• replyToComment — write: Reply to a comment thread.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.