Can I store the actual video file in the Media Bridge?

No. The Media Bridge stores metadata, properties, and engagement events about media that lives on the integrator's platform. Video and audio bytes remain on the integrator's CDN; HubSpot only references them by ID.

What are the rate limits for the Media Bridge API?

It shares HubSpot's standard public API caps: 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for Private Apps on Pro and Enterprise. High-volume event ingestion should be batched where possible to stay under those limits.

How do I send a play event for a specific viewer through Jentic?

Run pip install jentic, search 'send hubspot media played percent event', load the schema, and execute it with the viewer's contactId, the mediaId, and the percentage played. Jentic posts to /media-bridge/v1/events/media-played-percent with the right auth headers.

Does the Media Bridge support custom event types beyond play percent and attention span?

Not in this spec. The two ingestion endpoints exposed are media-played-percent and attention-span. For richer behavioural tracking, pair Media Bridge with HubSpot's Custom Events API, which supports arbitrary event definitions.

Can I limit what my agent is allowed to do with the HubSpot Media Bridge API?

Yes. Because you self-host Jentic One, your own rules decide which Media Bridge operations the agent may call and which HubSpot credentials it may use. Since the app id sits in the URL path (/media-bridge/v1/{appId}/...), a rule can pin the agent to a single media app so it can register that app's settings and define its schemas but nothing else. You expose only the operations you choose, so streaming media-played-percent and attention-span events is available only if you include it, and batch-archiving properties stays off unless you allow it.