We would like to hear about your API design situation.
Whether you have a specific question, want to discuss a potential audit, or simply want to understand whether this platform is relevant to your team, we are happy to have that conversation.
A few things worth thinking about before you reach out.
Conversations go further when both sides have some context. These are not prerequisites, just prompts that tend to make the first exchange more useful for both of us.
Know roughly what you have
A rough sense of your API's scope, whether it is public or internal, how many teams consume it, and whether you have any existing style guide or design standards will help us understand your starting point quickly.
Have a sense of what is not working
It does not need to be a precise diagnosis. Even a general feeling, like "our reviews feel inconsistent" or "integrators keep asking the same questions", gives us something concrete to start from.
Think about who else is involved
API design review typically involves more than one role. Knowing whether this is a solo initiative or something you want to build across a team helps us suggest the right scope and format for a first engagement.
Consider your timeline
Is there a product release coming up where API design quality matters? Are you in early planning or mid-development? Timeline context helps us understand whether a quick audit or a longer educational engagement is the right starting point.