For the reason that Mannequin Context Protocol (MCP) was introduced by Anthropic a 12 months in the past, we’ve seen immense progress in giant language fashions (LLMs) and agentic use circumstances. Earlier than MCP turned the de facto agentic customary, builders constructing brokers on high of LLMs must hard-code the connective tissue between the LLM and apps. Builders would wish to construct customized integrations between their LLM shopper and the apps required by an finish consumer’s immediate. With MCP, builders can now join immediately with exterior knowledge sources, so their LLM can learn knowledge from and write knowledge to the linked functions.
However there’s a breaking level the place issues begin to disintegrate. The robustness and efficacy of agentic options depend upon the standard of the applying programming interfaces (APIs) which might be utilized by an MCP server. MCPs expose instruments which might be invoked by LLMs, and these instruments typically reference particular person API endpoints. The standard of APIs, due to this fact, immediately correlates with the LLM shopper’s correct discovery and execution of consumer prompts.
The hierarchy of developer wants
Delivering high quality, constant, and intuitive APIs is a matter of a company’s cultural priorities. At Cisco, we’re lucky to have government management sponsorship of our platform API floor space, which helps us ship high quality APIs throughout the enterprise.
We’ve discovered that it’s useful to prioritize API roadmaps based mostly on a hierarchy of developer wants.
Maslow’s hierarchy of wants illustrates the speculation that human motivation is pushed by 5 ranges of want. Organized in a pyramid, these are: physiological, security, love/belonging, esteem, and self-actualization. The idea means that individuals are motivated to satisfy primary wants first earlier than progressing to higher-level wants for self-fulfillment.
Our hierarchy of developer wants takes Maslow’s pyramid and extends it to rank developer ache factors and options in line with primary wants, enterprise wants, and vertical or industry-specific wants.
The foundational components: API protection and completeness
The developer hierarchy of wants affords a framework for our product and engineering groups to prioritize their roadmaps. For instance, the inspiration of API high quality is predicated on protection or completeness. With out extant API endpoints, nothing upstream issues—not documentation, code samples, nor developer relations efforts.
Determine 1: The hierarchy of developer wants affords a framework for product and engineering roadmap prioritization.
Subsequent comes the necessity for a high-quality OpenAPI Specification (OAS) and the interior engineering API growth lifecycle. An OAS file may have a lot of APIs, but when the prose round every endpoint is sparse, or sure endpoints are lacking schemas and documented parameters, then it forces builders to both guess and check or reverse engineer which capabilities every API endpoint serves via rote testing. Each choices supply a poor developer expertise.
It’s necessary for any group with a developer movement to spend money on linting and static evaluation of latest APIs being developed, in order that inside engineers can simply ship new API performance with out being consultants within the API framework. An excellent instance of that is Cisco DevNet’s open-source software, API Insights, which permits builders to audit their API specs to implement finest practices as early as attainable within the growth cycle. Additionally, many individuals aren’t conscious that if the OAS is lacking schemas, it primarily means software program growth kits (SDKs) and infrastructure as code (IaC) instruments like Terraform and Ansible can not use these endpoints—no matter their launch standing—since SDKs and IaC instruments require the flexibility to auto-generate tooling from the OAS.
The ethical of the story: All issues depend upon OAS, particularly AI.
Documentation and scalability
The subsequent degree of significance is having intuitive documentation. In case your APIs are unbelievable however nobody can discover which one does what, or your info structure is a nightmare, it negates the trouble your group put into delivery high quality APIs and OAS. Builders are usually not monoliths. Some are profession software program engineers, however many, particularly within the networking {industry}, are technical professionals like networking engineers who’re studying tips on how to write scripts or construct primary net apps utilizing REST APIs for the primary time of their profession. Accordingly, nice developer documentation is a must have earlier than anybody can perceive what is feasible for an AI agent use case.
Shifting to the following degree of developer wants, now we have enterprise scale and high quality. Organizations that promote to Fortune 500 corporations or brownfield enterprises know that scale and the CIA-triad (confidentiality, integrity, availability) are mission-critical tenets. These tenets should be assured earlier than builders will really feel comfy constructing customized options on high of an API, no matter whether or not these options are conventional scripts, app integrations, or agentic troubleshooting options.
At Cisco, we’re proud to intently companion with our largest prospects and managed service supplier companions to make sure that our platform works easily for everybody, from a mom-and-pop brick-and-mortar store to a Fortune 100 world conglomerate that wants redundancy, immense scale, and fee limits, in addition to the very best uptime accessible.
Simplifying API consumption and vertical software
Our penultimate degree of developer wants is the place we get into abstraction and obfuscation to simplify how APIs are consumed. SDKs and IaC instruments like Ansible and Terraform are the bread and butter of enormous enterprises that require widespread automation. IT groups are rising leaner, and networking engineers are anticipated to do extra with much less. If all different developer wants have been met, it turns into straightforward for a company to generate and keep SDKs and developer instruments like an MCP server.
For instance, Cisco Meraki and Cisco Catalyst Heart each keep high quality OAS recordsdata, which prospects can use to generate an MCP server inside a couple of minutes with standard API instruments like Postman. This enables a developer who’s attempting to construct a customized agent to have the ability to accomplish that in days, not weeks or months, all due to the standard of our APIs, OAS, and docs, and our potential to make sure that high quality at enterprise scale.
Lastly, what actually makes a developer platform shine are code samples and integrations. If all different developer wants are met, this creates an ecosystem situation the place builders can simply create new scripts, integrations, and instruments and share them with the platform group within the type of code samples, libraries, and integrations.
Finally, delivering full, high-quality APIs, strong documentation, and an engaged ecosystem lays the groundwork for innovation and ensures that agentic options can attain their full potential.
