AI writes the code. Reminix makes it safe to share.

Your team has scripts on laptops and in repositories, and more every week now that AI writes them. Today, only the person who wrote one can run it. Publish it to Reminix and anyone on your team can: support, finance or operations fill in a form, your software calls an API, and agents use it as a tool. Who can run it, which keys it gets and which runs need approval are settings, not code.

Start free Read the quickstart

Refund customer

Refunds a card payment in full.

Payment IDpi_3QK8hT2eZvKYlo2C

Run

Run by Dana from the app, version 4. Succeeded in 1.2 seconds.

refund-customer

Support team may run it
Stripe key: api.stripe.com only
Approval: when an agent runs it

A script is one function

Publish it with reminix scripts publish. The Stripe key lives in Reminix, which attaches it only to requests to the host you allow.

refund-customer/index.ts

export default async function run(
  inputs: { paymentId: string },
  ctx,
) {
  ctx.log(`refunding ${inputs.paymentId}`);
  // No key here: Reminix adds it to
  // requests to api.stripe.com.
  const res = await fetch(
    "https://api.stripe.com/v1/refunds",
    {
      method: "POST",
      body: new URLSearchParams({
        payment_intent: inputs.paymentId,
      }),
    },
  );
  return await res.json();
}

One publish, every way to run it

The inputs you describe become the form, the API's request and the agent's tool, so every way of running it checks the same things.

refund-customer

Input: paymentId

People on your teamA form in the app, made from the inputs
Your softwarePOST /v1/scripts/refund-customer/runs
Your terminalreminix scripts run refund-customer
AI agentsA tool over MCP: refund_customer
A timetableA schedule, such as weekdays at 9:00
Something that happenedA trigger, such as another run failing

The parts that are easy to get wrong

Sharing a script is easy. Sharing it safely is the hard part, and it's what Reminix does for you.

An API key in the code

You save a key once, and Reminix never shows it again. Reminix attaches each one only to the hosts you allow, and the code never holds it.

Code that calls somewhere unexpected

A script has no network until it lists its hosts, and every request it makes is in the run's log.

An agent running the wrong thing

Set a script so agents' runs wait for an owner or admin. On Business, every run can wait for approval.

A change that breaks it

Every change is a new version, and nothing goes live until someone publishes it. Rolling back is publishing the version before.

Who can run what

Share a script with everyone, or only with certain teams. Others don't see it at all, not even through the API.

Every run on record

The Runs page shows every run across the team: which script, how it ended, how long it took, and whether it came from the app, the API, a schedule or an agent. Each run opens to its inputs, output and log.

Reminix's Runs page: a week of runs across five scripts, each with its status, duration, and whether it came from the app, the API, a schedule or an agent.

Your coding agent can do the porting

Connect Claude Code or Codex to Reminix's MCP server and paste a prompt like this one. It writes the script, tests a draft, and publishes only when you say so.

How it works, step by step

Prompt

Publish scripts/refund.py to Reminix. Search the team's scripts first in case one exists. Describe its inputs, write a short README, keep every secret out of the code and declare only the hosts it calls. Upload it as a draft, test-run it, show me the result, and ask me before publishing.

Pricing

You pay for authors, the people who write or publish scripts. People who only run them are included: 10 on Free, 25 on Team, and any number on Business.

Compare the plans

Plan	Price	Runs a month
Free	$0	1,000
Team	$20 per author a month	10,000
Business	$50 per author a month	100,000

Start with the free plan

Free for up to 3 authors. No card needed. Reminix is in beta, and we read every message.

Start free Talk to us