I struggle to share the entirety of my vision for API governance as it requires prior awareness of multiple API specifications and the current state of gover...
API design guide | Cloud API Design Guide | Google Cloud Documentation
A set of guidelines for designing APIs that are consistent with Google AIPs.
How AI Agents Are Changing API Architecture | daily.dev
Autonomous AI agents are reshaping API consumption patterns, prompting API providers to rethink identity, authorization, security, design, and observability....
Optimised API Management for the modern business
Join us as we unveil the path to optimised API management, tailored for modern enterprises.
Semantic governance policies overview | Gemini Enterprise Agent Platform | Google Cloud Documentation
Learn how Semantic Governance Policies (SGP) secure AI agents and tool calls using Natural Language Constraints.
Almost everyone is doing the API economy wrong | TechCrunch
It’s time to hold companies to a higher standard when it comes to APIs. As software "eats the world," it seems like it’s not enough for a business to just serve its customers and hopefully make a profit, they also have to be “platforms” -- and, as any developer would respond, these days you just can’t be a platform without an API.
Intro to API for Developers | Namecheap.com
Provides information about environments, how to enable api and a general overview
Pacing the Frontier | Gillian K. Hadfield
The Pacing the Frontier letter calls on the US government to support an international effort to build the technical and governance tools needed to protect our option to pace AI development. I and others have been working on the problem of how to build such infrastructure for ten years, including participating in dialogues on AI safety with Chinese academic colleagues during the past three. Here are my suggestions: 1. Don’t rely on off-the-shelf models like FINRA and the FDA which were built for 20th Century single-domain government expertise. They’re not fit for purpose. 2. Don’t act like no-one’s thought about the AI governance problem before. We’ve spent two years refining a regulatory markets design into working legislative language, for example, and it’s now in AI governance bills in five states and in Congress. 3. Don’t try to write an exhaustive set of rules for AGI first. 4. Pick a domain that can achieve widespread global consensus to start. Mine would be recursive self-improvement: models should not build models. Build the technology that verifies that. 5. Focus relentlessly on building flexible verification infrastructure that is able to enforce whatever rules we can ultimately agree on. 6. Don’t assume we already know how to do this and governments can just write tests into law. Technology needs to be built and by the private sector. 7. Don’t wait for the infrastructure to emerge first. The components and people are there and the ecosystem can scale fast with the right incentives. 8. Incentivize large-scale investment in verification technology by building a governance structure and industry funding that creates a market for private verification organizations. 9. Use licensing and public oversight to ensure verifiers are independent of the frontier labs. 10. Protect sovereignty by enabling each government to license its own verifiers from a global market of verifiers recognized by other countries. 11. Leverage the incentive of global trade for models and model services by requiring verification for market access. 12. Just start. Sources in comments.
A primer on the reality of working with APIs as a new developer
A rundown of some of the issues and realities you'll find moving from education to real-world applications involving APIs.
Why Executive Interest In APIs Is Booming
A decade ago, API awareness was limited, with evangelists educating a mostly unaware C-suite. Today, APIs are integral to business, widely embraced by executives and developers alike, reflecting a significant shift in digital transformation strategies.
API Improvement Proposals
AIPs are design documents that summarize Google's API design decisions. They also provide a framework and system for others to document their own API design rules and practices.
</> htmx ~ Hypermedia APIs vs. Data APIs
In this essay, Carson Gross explores the fundamental differences between hypermedia APIs and data APIs, He explains how hypermedia APIs, which return HTML over HTTP, can embrace frequent changes due to their self-describing nature, while data APIs require more stability and versioning to avoid breaking client code. Carson argues that these distinct characteristics should inform different design approaches for each type of API.
Replacing Middle Management with APIs by Peter Reinhardt
There’s a trend in Silicon Valley startups to create a software layer in industries that were traditionally pure human services. Uber and Lyft have created software layers in the taxi industry, 99designs Tasks in the visual design industry, Homejoy in the cleaning industry, and so on. These new software services employ armies of human workers, optimizing their output, productivity and quality while driving price down.
Technical Charter
This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, Open Responses (the “Project”), an open, vendor-neutral specification for large language model APIs.
