This is blog post on the AI Context use case, focusing on providing Model Context Protocol (MCP) servers on top of common private, public/1st party and 3rd party APIs, as well as local SQL databases, employing a domain-driven, declarative, and governed approach to right-sizing the context windows via MCP while providing integrations for us across AI copilots and agents.
This is blog post on the capturing the conversation with Mike Amundsen and Kevin Swiber on the Naftiko Capabilities podcast, helping connect our hypermedia past with this AI integration moment.
Do a fresh round-up of the schema tooling available. Specifically for the standards we are supporting, beginning with JSON Schema, but then also focusing on each of the specs and how their schema are managed or not. Round-up tooling, evaluate and apply metadata, and add to tooling section and link to any relevant standards, then publish a story on the subject.
Established thinking in large organisations has been to focus API reuse goals and metrics on internal, in-house produced APIs. The logic is straightforward: build once, reuse everywhere, and maximise the return on investment for internally developed services. However, recent insights suggest we’ve been looking at API reuse through the wrong lens. The real opportunity—and the real risks—lie not in producer-side reuse, but in how we enable engineers to consume our and third-party APIs efficiently, securely, and with proper governance.
Avalara asked me to take a look at their API portal and provide feedback on their API experience – which resulted in pretty compelling review and will continue with a deeper dive on their APIs and MCP servers. I will then explore the possibilities for using as part of our AI orchestration use case because this is where they appear to be at in their journey.
This is blog post being written and published by The New Stack on capabilities. We have already done the interview with them and shared relevant capabilities thinking stories from the ecosystem, and they will be working on first part of January, and then publishing it with a link to our Naftiko Signals onboarding landing page to drive conversations.
This is blog post announcing the Naftiko Capabilities blog post, providing an introduction to why we are doing the podcast and the central role that capbilities will play in the conversation. Our goal is to talk about the technical details of integration and automation, while ensuring we are aligned with business outcomes.
This is an introductory blog post to help us begin sharing stories of what the Nafitko Engine could be, helping stimulate more conversation around gateways, and what we are looking to build with engines, helping shape our road map, but also the go-to-market effort around what is possible with engines.
This is an introductory blog post on the Naftiko Fabric to get the conversation going around what we are building, helping connect the dots with capabilities, and support Jerome’s talk at APIDays, and the conversation we are having with folks about what is needed when it comes to integrations and automation.
This is blog post for API Evangelist, announcing Naftiko, building upon what we did in December, helping continue get the word out about what we are building, taking another shot at explaining what we do to the community, and catching more people who may not have seen the original announcement and press release within the API Evangelist community.
This was the press release to announce the launch of Naftiko as a company and the funding announcement, showing the team, and what we are building, drawling a public line in the sand for when Naftiko was launched at APIDays, helping provide material for other channels and outlets to syndicate, while helping build attention to what we are doing.
This is blog post announcing the Naftiko Signals program on the Naftiko Blog, providing an official line in the sand for when we started the program, while we are still building it out in the public, helping share the backstory, the data, and bring in more design, service, and market partners to help us invest in the research.
This was a white paper to support the Naftiko Signals workshop at APIDays, and provide more content for the website as we work to launch the company, helping share why signals from enterprise systems can help us understand what is happening, and can be use to steer any system in the desired direciton and achieve the business outcomes required.
This is an introductory blog post on the Naftiko blog sharing our perspective on capabilities, publishing early views on what capabilities are to help stimulate other conversations as we continue to work to shape what a capability could be and develop our schema that can be used to support the Naftiko Framework, Engine, and Fabric.
This is a blog post announcing Naftiko in the lead up to APIDays and after the launch of our website, announcing the company, funding, and team behind, providing a snapshot of what we are building and get the conversation started with the ecosystem about what is needed when it comes to API and AI integration.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.