api·for·any·site

Give Claude, ChatGPT or Grok Bot an API for the web, even for the sites that never built one.

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, running in your own logged-in browser.

Add to ChromeFree and open source · GitHub

Without a kit · the agent drives the page
open linkedin.com/mynetwork
screenshot, read it
scroll
screenshot, read it
click "Show all"
wait for the page
screenshot, read it
the layout changed, retry
screenshot, read it
scroll
screenshot, read it
type out the list
40.7 s · 129k tokens · $1.03
With the LinkedIn kit · one call
list_invitations()
[
  { name: "Ada Quill",
    headline: "Growth at Larkspur",
    note: "Loved your post on…",
    mutual: 12 },
  { name: "Tomas Reyes", … }
]
1.4 s · 1.2k tokens · $0.01

Examples of automations you can now run

Two website kits ship with the extension. You ask your agent; it calls the kit.

  • "Triage my LinkedIn invitations. Accept the people I have met, ignore the pitches."

    linkedin list_invitations() accept_invitation(id) ignore_invitation(id)

  • "Brief me on what happened overnight in the subreddits I follow."

    reddit list_posts(subreddit) read_post(permalink)

  • "Who is waiting on a reply from me on LinkedIn, and what did they ask?"

    linkedin list_conversations() read_thread(id)

Ask your agent to build an API for any site

No kit for a site you use? Ask your agent to write one. A kit is a manifest and one small file per tool, and it installs from your own machine.

› Write me a kit for Hacker News that lists the stories I upvoted.
read how kits are built
write kits/hackernews/manifest.json
write kits/hackernews/tools/upvoted_stories.js
install it from this machine
upvoted_stories() → 23 stories

Safe by design

Kits run in your browser, on your own session. Catalog kits are reviewed code shipped with the extension. A kit you write yourself runs under a browser fence.

  • A kit runs only on its siteYou grant that site when you install the kit. It cannot run anywhere else.
  • Your own kits are fencedA kit you write runs in an isolated world that can only reach its own site, so it cannot send your data anywhere else. The only exit is the result handed to your agent.
  • Changes need a switchTools that accept, ignore or remove are marked and need a switch you turn on per kit. Nothing sends messages on your behalf.
  • Every call is logged and cappedDaily limits you set. When a cap is hit, the tool stops.
  • No server of oursYour agent and the extension meet on your machine. Kits come from the reviewed catalog or your own computer, never from a link someone sends you.
  • Open sourceThe extension, the runtime and every catalog kit are on GitHub.