An AI Agent Walks Into a Streaming Platform
Most video platforms assume a person is at the keyboard. Signup wants an email address and a click on a verification link, billing wants a card, and when something goes wrong the answer is a support ticket. An AI agent can do none of those things. It can hold a wallet, sign messages, call an API, and read structured errors.
FrameWorks lets an agent become a paying customer with only those abilities. It signs in with a wallet, sets up what it needs at zero balance, and pays for usage in USDC when a billable call asks for it.
One agent’s first run
Section titled “One agent’s first run”Say an agent has been asked to publish a finished video on FrameWorks. It has never used the platform and has no account.
It starts with an EVM wallet. It asks FrameWorks for a one-time login message, signs it with the wallet’s key, and sends the signature back. That signature is the whole signup. The first successful sign-in creates an account tied to that wallet, with no email address and a balance of zero.
At zero balance the agent can already do a lot: read its account status, create API credentials, configure a stream, and look up what the platform offers. None of that costs anything, so none of it needs money.
Then it asks to create the upload. Processing a video is billable work, and the balance is empty, so the call comes back with HTTP 402 Payment Required and a payment offer bound to this account: the amount, the token, and the networks it can pay on.
The agent signs a USDC transfer authorization for that amount and submits it as a top-up. FrameWorks relays the transfer, so the agent does not need to hold gas, waits until the chain confirms it, and credits the balance. The agent retries the upload, the usual balance and account checks run again, and the upload is created.
No step in that run needed a person. The agent never read an email, typed a card number, or waited for support.
Why payment is part of the API
Section titled “Why payment is part of the API”The x402 protocol gives the 402 status code a machine-readable body: what to pay, how, and where. An agent that hits a billable call without funds gets a structured answer that names the fix and carries the offer to pay it, so it does not have to parse an error message written for humans.
We settle on Base and Arbitrum. We skipped Ethereum mainnet, because a few dollars of gas per transaction makes no sense for topping up a streaming balance. Agents, or people, who prefer a plain transfer can use a deposit flow instead: ask for a quote, get a deposit address, and send ETH or USDC to it.
What a wallet-only account can and cannot do
Section titled “What a wallet-only account can and cannot do”A wallet costs nothing to create, so a wallet-only account is always prepaid: it has to fund its balance before it consumes anything billable. That is what stops someone from minting thousands of wallets and running work on credit. Adding and verifying an email address later opens the other billing options.
Payment and identity stay separate. Paying never signs an agent in, and a payment does not override a suspended account; after the top-up, the retried call goes through the same checks as any other request. Usage is metered and itemized the same way whether the caller is a person or an agent.
The cost of this model for the agent’s operator is that the wallet is the account. Whoever holds the key controls the account and its balance, so the key belongs somewhere the agent can use it and nothing else can read it.
One MCP surface for the whole platform
Section titled “One MCP surface for the whole platform”Once signed in, the agent works through the MCP server: tools for streams, clips, DVR, VOD, playback, quality diagnostics, billing, and support, plus read-only resources for account and stream state. A small part of it is public, covering sign-in and playback lookup, because an agent has to be able to find out how to become a customer before it is one.
Skipper, the AI video consultant, is available on the same surface for questions such as why a stream is buffering. It can search documentation and run diagnostics but cannot change anything on that path, so asking it a question never deletes a stream as a side effect. Changes go through the dedicated tools, each with its own authorization. We wrote about Skipper when it launched.
The agents overview is the place to start. Wallet authentication and agent payments cover this post’s flow step by step, including the payment networks, the deposit flow, and the errors an agent should expect.