---
title: "Beat API (@beatapi) | Hashnode"
description: "Founder of BeatAPI — OpenRouter for Agents. Read the latest articles by Beat API on Hashnode."
url: "https://hashnode.com/@beatapi"
---

@beatapi

# Beat API

@beatapi · Shanghai, China · Joined July 2025

Founder of BeatAPI — OpenRouter for Agents

### [Let your AI agent work in your signed-in Chrome](https://vogueai.hashnode.dev/let-your-ai-agent-work-in-your-signed-in-chrome?utm_source=hashnode&utm_medium=feed)

The account is already signed in. The editor is open. You have a draft ready, and you want your agent to pick up the work from there. BeatBrowser connects a local MCP-compatible agent to a selected Ch

4 min read · [vogueai.hashnode.dev](https://vogueai.hashnode.dev/let-your-ai-agent-work-in-your-signed-in-chrome?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/let-your-ai-agent-work-in-your-signed-in-chrome/6ad998d61254e611c94a73cd)

### [A local video project you and your AI agent can both edit](https://vogueai.hashnode.dev/a-local-video-project-you-and-your-ai-agent-can-both-edit?utm_source=hashnode&utm_medium=feed)

You ask your agent to adjust a caption. Then you want to open the timeline, inspect the change, and make another edit yourself. That is the handoff we are building BeatDesign for. It is an open-source

4 min read · [vogueai.hashnode.dev](https://vogueai.hashnode.dev/a-local-video-project-you-and-your-ai-agent-can-both-edit?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/a-local-video-project-you-and-your-ai-agent-can-both-edit/6ad99820de4b9294c7f34959)

### [Connecting MCP agents to existing Chrome: the design behind BeatBrowser](https://vogueai.hashnode.dev/connecting-mcp-agents-to-existing-chrome-the-design-behind-beatbrowser?utm_source=hashnode&utm_medium=feed)

How a Chrome extension and local bridge connect MCP agents to existing sessions, with visible tasks, human takeover and optional remote access.

4 min read · [vogueai.hashnode.dev](https://vogueai.hashnode.dev/connecting-mcp-agents-to-existing-chrome-the-design-behind-beatbrowser?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/connecting-mcp-agents-to-existing-chrome-the-design-behind-beatbrowser/6ad4beeacb5ce49aaaad0fbd) [Oct 18](https://hashnode.com/posts/connecting-mcp-agents-to-existing-chrome-the-design-behind-beatbrowser/6ad4beeacb5ce49aaaad0fbd)

### [Gemini 4 Argon API: 5 Integration Traps Behind the 1M-Token Headline](https://vogueai.hashnode.dev/gemini-4-argon-api-agent-migration?utm_source=hashnode&utm_medium=feed)

Five Gemini 4 Argon API integration traps: shared context, thinking limits, long decode, token billing, and cost per accepted agent task.

14 min read · [vogueai.hashnode.dev](https://vogueai.hashnode.dev/gemini-4-argon-api-agent-migration?utm_source=hashnode&utm_medium=feed)

[Oct 13](https://hashnode.com/posts/gemini-4-argon-api-agent-migration/6ace6cdd75bcc9ac7f91742b)

### [Three contracts to check when an agent uses models and web data](https://vogueai.hashnode.dev/three-contracts-to-check-when-an-agent-uses-models-and-web-data?utm_source=hashnode&utm_medium=feed)

An agent workflow can succeed at the model call and still fail at the task. I find it useful to separate three contracts before scaling a workflow. 1. The output contract Write the expected structure

2 min read · [vogueai.hashnode.dev](https://vogueai.hashnode.dev/three-contracts-to-check-when-an-agent-uses-models-and-web-data?utm_source=hashnode&utm_medium=feed)

[Oct 10](https://hashnode.com/posts/three-contracts-to-check-when-an-agent-uses-models-and-web-data/6ac9d0bd7bb4f590f98922a0)
