Render + Memtro

Only when you ask, and only what it has been granted: deploy a Render service now (latest commit, a given commit or image); cancel an in-progress Render deploy; roll a Render service back to an earlier deploy; restart a Render service; suspend a Render service (takes it offline); resume a suspended Render service; scale a Render service to a fixed number of instances; run a one-off job (a command) on a Render service; cancel a running Render one-off job; trigger a Render cron job run now; cancel a running Render cron job run; purge a Render web service's edge cache. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Render records into memory as entities.

API key. In dashboard.render.com open Account Settings → API Keys and choose Create API Key. The key reaches every workspace your user belongs to, with your access, so it can do whatever your user can.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Render for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.