annotated
Sign in
Browser_capture walkthrough · API + MCP + Chrome · 30 seconds

From agent request to inspectable receipt.

This narrated flow shows the browser_capture path: plain-language moment search hands a locked range to Chrome, waits for human approval, and returns bounded evidence.

Rendered from the current 1.2 product contract

Ask → ground → review → record → receipt

0:30

The deliberately synthetic, ElevenLabs-narrated walkthrough illustrates the shipped agent API, MCP tools, prepared-range browser_capture handoff, explicit browser capture boundary, and private artifact receipt. Example content is labeled and no live job runs in the video.

Read the full 30-second transcript
  1. Annotated for agents.
  2. Ask: find and clip where Jason talks about cool hunting.
  3. Annotated grounds the request in the source captions, returns the exact passage, then waits.
  4. You review the locked range, record only that moment, and send it back.
  5. The agent receives a clip and an inspectable receipt. Not a transcript dump. Not invisible automation.
  6. Find by language. Share by consent. Evidence with a human stop line.
  7. Yeehaw.

Need an audio-only source? Open the rights-cleared podcast fixture.

01

Find by language

The API or MCP returns bounded, verbatim caption windows with source and transcript fingerprints.

02

Browser stop for a person

On browser_capture, the handoff locks the chosen range; recording, rights confirmation, and Send remain explicit clicks.

03

Return inspectable proof

The agent receives the clip plus a receipt binding its source, range, capture method, rights basis, and bytes.

What this demonstrates: on browser_capture, finding a moment does not grant capture rights; the person reviews the exact range, records visibly, and sends separately. The separate authorized_remote path is caller-declared for directly fetchable media, is validated by the worker before any artifact is created, and uses an explicit delegated key-holder attestation with no browser check. Either receipt records provenance, not truth or verified rights.
Read the permission details
Try the complete product

Let agents find the evidence. Keep every capture boundary explicit.

Install the Chrome extension