Skip to content

fix(media-use): tag avatar-video heygen recipes with X-HeyGen-Client-Source#2391

Merged
miguel-heygen merged 1 commit into
mainfrom
worktree-media-use-video-client-source
Jul 14, 2026
Merged

fix(media-use): tag avatar-video heygen recipes with X-HeyGen-Client-Source#2391
miguel-heygen merged 1 commit into
mainfrom
worktree-media-use-video-client-source

Conversation

@miguel-heygen

Copy link
Copy Markdown
Collaborator

What

Add --headers "X-HeyGen-Client-Source: media-use" to the generating heygen video create recipes in skills/media-use/references/operations.md (avatar video + image-to-video), plus a note requiring it on any generating heygen command.

Why

media-use's avatar-video path is agent-driven — the skill instructs the agent to run heygen video create directly (no wrapper script). Those recipes went out untagged, so media-use avatar / image-to-video usage landed in master_video_table as generic cli:<agent> traffic with no client_source — i.e. not attributable to media-use, and invisible to a media-use dashboard slice. This closes that gap so avatar-video free usage is measured alongside TTS (#2365) and the CLI (#2368).

How

  • --headers "X-HeyGen-Client-Source: media-use" on both heygen video create recipes. It's the CLI's allowlisted attribution header and a persistent flag, so it works on every subcommand and can't override the reserved X-HeyGen-Source free-gate header.
  • Prose note generalizes it to video create / avatar create / video-translate; read-only discovery (avatar list, voice list) is explicitly exempt.

Test plan

  • Docs/recipe change only — no code. Verified both generating recipes now carry the header and code fences stay balanced.

Pairs with

Backend persistence #41968 (allowlist already includes the values); once merged, tagged avatar videos carry client_source=media-use in master_video_table.metadata, queryable via mvt.metadata:client_source in API Dashboard V3.

…Source

The agent-driven video recipes (heygen video create) went out untagged, so
media-use avatar / image-to-video usage landed as generic cli traffic and
wasn't attributable to media-use. Add --headers "X-HeyGen-Client-Source:
media-use" to the generating recipes (persistent flag, allowlisted by the
CLI) so those videos carry client_source in master_video_table meta and show
up in the API dashboards alongside the TTS path (#2365) and CLI (#2368).
@miguel-heygen
miguel-heygen merged commit ca7c017 into main Jul 14, 2026
36 checks passed
@miguel-heygen
miguel-heygen deleted the worktree-media-use-video-client-source branch July 14, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant