API for Any Site

Give your AI agent direct tools for the sites you use, running in your own browser. Install a website kit per site. LinkedIn first.

Your AI agent has no built-in tools for most websites, so it improvises: it reads the page, screenshots it, clicks around. That is slow, it breaks when the page changes, and it costs a lot of tokens. API for Any Site gives your agent direct tools instead. You install a website kit. A kit is a small set of scripts, one per tool, that run inside your own logged-in browser tab. Your agent then calls "list my invitations" as one fast call rather than reading and clicking through a page. How it works 1. Install a website kit from the catalog in the extension. LinkedIn is the first one. 2. Point your agent at the extension once. Any agent that speaks MCP works, including Claude Code. 3. Your agent calls the kit's tools. Each call runs in a background tab in your browser, at human pace, capped by daily limits you set, and every call is logged. What a kit can and cannot do A kit runs only on the site it declares, and only after you grant that site at install. Tools that change something (accept, ignore, remove) are marked as such and need a switch you turn on per kit. Nothing sends messages on your behalf. Where kits come from Two places, and nowhere else. The catalog: every kit in it is open source, reviewed, and shipped inside this extension, so what runs is what Google reviewed. Your own machine: you, or your agent, can write a kit for a site the catalog does not cover and install it locally; a kit you write runs under a browser fence that can only reach its own site, so it cannot send your data anywhere else. Kits are never installed from a link someone sends you. The LinkedIn kit List pending invitations with the note the person attached and mutual connections, accept or ignore one, list recent conversations, read a thread, remove a connection. Built for the "accepted, then they pitched me" triage. What you need Chrome 138 or later, and a small local program (the native messaging host) so your agent on the same computer can reach the tools. There is no server of ours in the loop; the agent and the extension meet on your machine. If you write your own kits, you also turn on "Allow User Scripts" once on the extension's details page; catalog kits do not need it. Free and open source: https://github.com/apiforanysite