MyteamOne API Client

If you've poked at the other four nodes in the ComfyUI-MyteamOne pack, you've seen this one's client output dangling off their inputs. The MyteamOne API Client is the keystone: it's the only node in the pack that touches your API key, and every Seedance 2.0 generation node downstream is dead weight without it.

What it actually is

It's not a generator. It doesn't render anything, doesn't use your GPU, and doesn't even make a network call the moment you hit Queue - it just assembles a small HTTP client object and hands it down the graph. When a generation node runs, it uses that client to POST your job, poll for completion, and stream the finished MP4 back. Think of it as the "load checkpoint" step for a model that lives in the cloud, not on your disk.

Why a model that lives in the cloud? Because ByteDance's Seedance 2.0 is closed - there are no weights to download, and an API is the only door. This pack routes through MyteamOne, a third-party reseller that resells Seedance cheaper than the official Volcengine pricing. The tradeoff is real: your key is a ak-... string issued by MyteamOne, and your prompts and media leave your machine for a server you don't control. That's the standard deal with API-wrapper nodes, and the community's "not local, no thanks" instinct applies - this is the right tool when you specifically want Seedance, the wrong default when a local model would do.

The four inputs

Only one is a secret:

• api_key - your ak-... key from myteamone.agione.pro. Leave it blank and the node fails fast with "Please set your MyteamOne API key."
• base_url - defaults to https://myteamone.agione.pro/hyperone/xapi/api/v1. Leave it.
• create_path - defaults to /videos. Leave it.
• poll_path - a URL template with a {taskid} placeholder, used to check on the job. Leave it.

The last three are exposed because the reseller's endpoints have shifted before, and the author would rather you edit a URL than wait for a release. If you start getting 404s, these knobs are your fix - the README says to check the current URLs with MyteamOne support.

The single output, client (type MYTEAMONE_CLIENT), isn't something you display. It wires into the client input of the Text-to-Video, Image-to-Video, Video-to-Video, and Multi-Reference nodes. Because it's a custom type, ComfyUI only lets you connect it where it's expected.

Install

The whole pack is one folder and one tiny dependency (requests) - no model downloads, because there's nothing local:

cd ComfyUI/custom_nodes
git clone https://github.com/agione-pro/ComfyUI-MyteamOne
cd ComfyUI-MyteamOne
pip install -r requirements.txt

Restart ComfyUI, then Add Node → MyteamOne. Or search "MyteamOne" in ComfyUI Manager.

Issues you'll actually see

The client's job is mostly error-message plumbing, so the failures are recognizable:

• 404 on create or poll - endpoints changed; update base_url / create_path / poll_path.
• Job hangs, then times out - generation legitimately takes a while. The create call alone can sit 60–180 seconds before it returns a task id, and polling can run up to 15 minutes. That's the cloud, not a hang.
• Windows ConnectionResetError [WinError 10054] in the logs - the API client's own notes call this a harmless teardown artifact after a successful response. Ignore it.

One last thing, and it matters: this is the node that holds your key, and the whole pack is a network-talking node by design. That's exactly the shape the ComfyUI ecosystem got burned by once (the LLMVISION credential-theft incident). This pack is open source and MIT - still, read what a node does before you hand it a key you'd hate to lose.