---
title: "Discussion on \"A short history of the CLI I built to stop curling IP APIs\" | Hashnode"
description: "Discussion on \"A short history of the CLI I built to stop curling IP APIs\". A short history of the CLI I built to stop curling IP APIs\n\nThe rhythm\nLet me start with the rhythm, because that is really where this tool came from.\nIf you have ever worked on anything involving IPs — abuse reports, rate limiting, geoblocking, susp..."
url: "https://hashnode.com/posts/a-short-history-of-the-cli-i-built-to-stop-curling-ip-apis-1-1/69e85cbd24a7de1c4682b8e3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A short history of the CLI I built to stop curling IP APIs](https://vineethnk.hashnode.dev/a-short-history-of-the-cli-i-built-to-stop-curling-ip-apis-1-1?utm_source=hashnode&utm_medium=feed)

A short history of the CLI I built to stop curling IP APIs The rhythm Let me start with the rhythm, because that is really where this tool came from. If you have ever worked on anything involving IPs — abuse reports, rate limiting, geoblocking, susp...

Apr 22 · 7 min read · vineethnk.hashnode.dev  
Read the article

-   [#cli](https://hashnode.com/tag/cli)
-   [#geolocation](https://hashnode.com/tag/geolocation)
-   [#ip](https://hashnode.com/tag/ip)
-   [#node](https://hashnode.com/tag/node)
-   [#open-source](https://hashnode.com/tag/open-source)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.