Module integration guide

Every robot ships with a curated set of official modules — Gmail, Calendar, todos, Docs, Sheets, and Slides today, with more certified over time. Official modules are reviewed, supported, and connected from the customer dashboard.

The catalog is not closed. We add official modules as we certify them, and we review community submissions for the same list.

If you want a tool we have not shipped yet, you can request it — or implement a module and submit it for review. Certified submissions join the official catalog; others may remain private to your workspace after we help you wire them up.

• Start from the example module below — it is the contract we review against.
• Describe tools in customer language. People talk to their robot, not to infrastructure.
• Anything that sends, posts, pays, or deletes must wait for the customer to approve.
• Request only the access the tool needs, and make disconnect remove keys and tokens.

Submit a manifest and a short demo script to hello@preferarobot.com. If you want us to build it instead, request a module.

Weather brief is a complete, reviewable example: one tool, no extra auth, copy a customer would actually say. Use it as the template for your first submission.

{
  "id": "weather-brief",
  "name": "Weather brief",
  "summary": "A short local forecast the robot can read aloud or drop into a morning note.",
  "auth": "none",
  "tools": [
    {
      "name": "weather_get_brief",
      "description": "Return today’s forecast for a city the customer names.",
      "input": { "city": { "type": "string", "required": true } },
      "approval": "none"
    }
  ]
}

The same example lives in the public preferarobot/modules repository. Fork it, fill in your manifest, and submit for review.