Interfaces

An interface is a promise about how two things will talk to each other, and most organizations have no idea how many promises they have already made. There are APIs bought, APIs inherited, APIs half-built by a contractor who has long since left, and open-source interfaces nobody remembers adopting. Before you build one more, it is worth knowing what you already have.

I map the landscape of interfaces across your operations — the commercial ones you pay for, the open-source ones you depend on, and the internal ones you have quietly accumulated. I document what each one does, where it fits, and whether it should exist at all. Where there is a genuine gap, I help you design a new interface deliberately, using OpenAPI and the wider API family, instead of inventing yet another one-off.

The work is not about chasing the newest protocol. It is about seeing the whole surface of how your systems connect, so you can make decisions about it on purpose rather than by accident.

What you walk away with

• A catalog of the interfaces your operations already rely on
• A clear read on overlap, gaps, and interfaces that should be retired
• OpenAPI-described designs for any new interfaces you genuinely need

Related reading

• Start by Mapping Your API Landscape
• Don’t Do Anything New — Just Map the APIs You Have
• Your Diverse API Toolbox
• API Discovery — the free tool for mapping the interfaces you already have
• APIs.io — search the wider landscape of public APIs