Finding capabilities

The Capabilities page is your team’s catalog. Before writing a new script, look there: someone may have built it already.

Search and filter

• Search as you type: words match the start of words in the name, slug, description and tags — rev mon finds “Monthly revenue report”.
• Tags: click a tag to see everything with it.
• Mine and Published only narrow the list.

The filters are in the page’s address, so you can share a filtered list. You only ever see capabilities you may use: a team’s capability stays hidden from people outside the team, in search too.

From the API (and so from agents, over MCP):

curl "https://api.reminix.com/v1/capabilities?q=refund&tag=finance&published=true" \
  -H "Authorization: Bearer $REMINIX_TOKEN" -H "X-Workspace: acme"

q returns the best matches first (one page); without it the list is newest first and pages with nextCursor. owner takes a user id.

Tags and README

Set tags in reminix.json ("tags": ["finance"] — they replace the capability’s tags when you publish a version) or in the capability’s Settings. Up to 10; lowercase letters, digits and dashes.

A README.md in the folder you publish from is kept with that version and shown on the capability’s page while it is published — what it does, when to use it, what its inputs mean. Markdown; raw HTML is not shown.

Who uses it

Every capability shows, for the last 30 days:

• runs, the share that succeeded, and when it last ran;
• where runs came from — the app, the API, the CLI, agents, schedules, triggers;
• people who ran it most;
• its schedules and triggers, and the other capabilities whose triggers run after it (on its run.completed or run.failed).

Before changing or retiring a capability, check who would notice.