kinbrowserdocs

Plugins and the marketplace (1.0)

Writing a plugin

A plugin is a folder with two files:

kin-plugin.json

{
  "name": "fx-rates",
  "version": "1.0.0",
  "description": "Exchange rates from the European Central Bank.",
  "verbs": {
    "rate": { "description": "The rate from one currency to others", "required": ["from"] }
  },
  "hosts": ["api.frankfurter.app"]
}

plugin.mjs

export default function (kin) {
  return {
    async rate({ from, to }) {
      const r = await kin.fetch(`https://api.frankfurter.app/latest?from=${from}${to ? `&to=${to}` : ''}`)
      return r.json()
    },
  }
}

What kin gives a plugin:

  • kin.run(verb, args) — any browser verb, under the same rules as an agent's (its own tabs, the public web, approvals, compliance).
  • kin.fetch(url) — only to the hosts the manifest names (and their subdomains), only to addresses agents may reach, redirects not followed.
  • kin.store.get(key) / set(key, value) — a small store of its own.
  • kin.log(...).

A plugin runs as code on the machine, like any app you install: only add plugins you trust. kin-browser plugins add ./fx-rates shows its verbs and hosts and asks before installing.

kin-browser plugins add ./fx-rates · plugins list · plugins remove fx-rates

Agents call plugin { name: "fx-rates", verb: "rate", args: { from: "MYR" } }; over MCP each verb is a tool of its own, plugin_fx_rates_rate.

The marketplace

Recipes and plugins from kinbrowser.com, each checked against its SHA-256 before it is installed:

kin-browser marketplace                     # list (--kind recipe|plugin)
kin-browser marketplace install fx-rates

To add yours, open a pull request adding a folder under marketplace/plugins/ or a library file under marketplace/recipes/ (see marketplace/README.md).