Get an API working once. Then let your whole team use it.

Reqlyn is an API workbench for your computer and a server you run yourself. Figure out an unfamiliar API, save what you learned as an operation with real inputs and outputs, publish it for your team, and hear about it when the API changes under you.

Install the desktopBuild your first operation →

GET  /api/v1/devices?site=north      →  Find device   (site → device, address)
POST /ipam/addresses/next          →  Reserve address (reads first, then writes)
                                          →  published as provision-edge v3
                                             run from the desktop, the command line, CI, an agent or MCP
Two requests turned into an operation, published as a version and run from anywhere
See a whole workflow and what flows through it. This operation finds a device in NetBox, reserves an address, opens a change in ServiceNow and posts to Slack. After a local test, every step shows its status and time, the steps that write are tagged, the Slack step is optional, and the drawer shows exactly what passed from address to change.See a whole workflow and what flows through it. This operation finds a device in NetBox, reserves an address, opens a change in ServiceNow and posts to Slack. After a local test, every step shows its status and time, the steps that write are tagged, the Slack step is optional, and the drawer shows exactly what passed from address to change.
See a whole workflow and what flows through it. This operation finds a device in NetBox, reserves an address, opens a change in ServiceNow and posts to Slack. After a local test, every step shows its status and time, the steps that write are tagged, the Slack step is optional, and the drawer shows exactly what passed from address to change.

From one request to something your team can run

Your requests and operations are the same on your computer, in Git and on your server. Nothing gets rebuilt along the way.

  • Get it working

    Bring in what you already have: OpenAPI, Postman, Insomnia, Bruno, HAR or curl. Or record a session in your browser. Your credentials stay in your operating system’s secret store.

  • Keep what you learned

    Turn requests into an operation on a canvas or in Arazzo, with typed inputs and outputs, retries, paging and waits. A step that writes can read first, so a preview shows you what it would change.

  • Publish and run

    A published version never changes, and a second person can approve it before it goes live. Run it from the desktop, the command line, CI, a private agent inside your network, or as an MCP tool.

  • Know when it changes

    Recorded cases replay before a version goes live. Drift checks against the API’s description, and an inventory of every API you call, show you what changed and who it affects.

Made for network teams and the systems around them

Sixty-eight signed, curated packs get you started, each one tested against its own fixture: Meraki, Mist, Juniper Apstra and Support Insights, Arista CloudVision, Cisco Catalyst Center, NSO and ACI, Nokia NSP, F5, PAN-OS, FortiGate, NetBox, Infoblox, BlueCat, IP Fabric, Forward, ThousandEyes, Zabbix, ServiceNow, PagerDuty, Vault, CyberArk, and more.

Skip the groundwork for the systems you already run. Eight curated packs are installed here, from Apstra and Infoblox to Meraki and Mist, with NetBox, PAN-OS, ServiceNow and Slack further down the list. The Meraki device operation’s regression cases, recorded from live runs, replay without sending anything, and every one passes.Skip the groundwork for the systems you already run. Eight curated packs are installed here, from Apstra and Infoblox to Meraki and Mist, with NetBox, PAN-OS, ServiceNow and Slack further down the list. The Meraki device operation’s regression cases, recorded from live runs, replay without sending anything, and every one passes.
Skip the groundwork for the systems you already run. Eight curated packs are installed here, from Apstra and Infoblox to Meraki and Mist, with NetBox, PAN-OS, ServiceNow and Slack further down the list. The Meraki device operation’s regression cases, recorded from live runs, replay without sending anything, and every one passes.
Catch the moment your inventory and your IPAM stop agreeing. This check lines them up by address and finds a name conflict, stale records, an address used twice and devices missing on each side. It plans the one write that fixes the conflict, and nothing is written until you say so.Catch the moment your inventory and your IPAM stop agreeing. This check lines them up by address and finds a name conflict, stale records, an address used twice and devices missing on each side. It plans the one write that fixes the conflict, and nothing is written until you say so.
Catch the moment your inventory and your IPAM stop agreeing. This check lines them up by address and finds a name conflict, stale records, an address used twice and devices missing on each side. It plans the one write that fixes the conflict, and nothing is written until you say so.

See every screen →

Yours to run

There’s no Reqlyn cloud and no telemetry. The desktop works fine on its own, and the server runs wherever you put it, reaching only the destinations you allow. A credential only goes to the origins you approve, and sync is encrypted end to end with your workspace key. See what leaves your computer.