---
type: "article"
title: "Weekly API Evangelist Governance (Guidance)"
newsletter: "API Evangelist"
newsletter_handle: "apievangelist"
newsletter_url: "https://usecommune.com/n/apievangelist"
author: "Kin Lane (@kinlane)"
published: "2025-03-03T16:24:24.195Z"
canonical_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-13"
markdown_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-13.md"
chat_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-13/chat"
source_url: "https://buttondown.com/apievangelist/archive/weekly-api-evangelist-governance-guidance-3638/"
body_source: "native"
likes: 0
replies: 0
body_words: 690
---

# Weekly API Evangelist Governance (Guidance)

*I would like to welcome our new*[*documentation partner Theneo*](https://bit.ly/41n9vPS)*, as well as give another weekly shout out to our*[*SDK partner APIMATIC*](https://bit.ly/3UFE1AP)*. API Evangelist storytelling occurs because of Theneo and APIMATIC, and I am thankful to have their support for this exciting ride!*

It was a productive week at API Evangelist. [19 separate stories on the blog](https://apievangelist.com/2025/) answering questions for people I am speaking with, building on conversations that occurred at Tyk’s LEAP 2.0 API Governance conference, and moving [API Evangelist Knowledge Builders](https://apievangelist.com/#knowledge) forward using open-source partner tooling.

There were a lot of lessons learned profiling [credit card providers](https://apievangelist.com/2025/02/24/what-stands-out-across-the-apis-for-the-seven-major-credit-card-companies/) and [automobile manufacturers](https://apievangelist.com/2025/02/26/learning-from-how-eleven-automobile-manufacturers-handle-their-public-api-presence/) this week helping continue to lay the foundation informing [the API pulse](https://github.com/api-evangelist/api-pulse), and identifying who is investing in their API presence at these top industry levels.

![](https://assets.buttondown.email/images/cbd041c8-67e1-4e45-8156-083eb72ce46d.png?w=960&fit=max)

*Do you?*

[Tyk is leading the API conversation](https://apievangelist.com/2025/02/28/tyk-is-leading-the-api-governance-conversation/), inviting me to [speak at their LEAP 2.0 API governance conference on Thursday](https://apievangelist.com/2025/02/24/join-api-evangelist-for-an-api-governance-conversation-this-thursday-at-tyks-leap-20/) — it was a great conference with a lot of smart people sharing their experience and expertise. It gave me hope to hear folks talk about how API governance is about people and business, and to a lesser degree about technology.

My talk at Tyk’s conference opened things up for the day, but was bookended a talk by James Higginbotham at the end of the day-—fueling my beliefs around [capital G Governance and lowercase g governance](https://apievangelist.com/2025/02/28/capital-g-governance-and-lowercase-g-governance/). After hearing other talks I feel that [the distribution of governance is a very murky topic for all of us](https://apievangelist.com/2025/02/26/the-distribution-of-apis-the-development-the-gateway-and-the-governance-guidance/)—which will need more work if are going to make progress. Outside API Evangelist, Bruno Pedro [published a convincing argument that API governance was more than rules automation](https://apichangelog.substack.com/p/api-governance-isnt-just-rule-automation).

[![](https://assets.buttondown.email/images/b7651e49-0310-45f9-8256-db21056df3ec.png?w=960&fit=max)](https://apievangelist.com/2025/02/28/capital-g-governance-and-lowercase-g-governance/)

*lowercase g governance*

Schema was a priority this week, with coverage of the [SourceMeta Schemas registry](https://apievangelist.com/2025/02/24/sourcemeta-schema-a-simple-json-schema-registry/), and [Sourcemeta founder Juan Cruz Viotti coming by for a conversation about why he built the registry](https://apievangelist.com/2025/02/27/api-evangelist-conversation-with-juan-cruz-viotti-of-sourcemeta-about-schema-registries/), but also discussed JSON Schema as a specification and the importance validation performance for the runtime — [schema work is the most stabilizing API work](https://apievangelist.com/2025/02/25/schema-work-is-the-most-stabilizing-api-work/).

Poking our head into the world of artificial intelligence, we felt compelled to push back a little on [AI providing more access to data](https://apievangelist.com/2025/02/28/ai-makes-data-more-accessible/), and had a good belly laugh about [our friends at Corewood fixing $7 haircuts](https://apievangelist.com/2025/02/24/corewood-fixes-dollar7-haircuts-aka-fixes-bad-code-generated-by-artificial-intelligence/) — aka generated AI code. We also have a conversation coming up this week to discuss [SDK generation using AI](https://apievangelist.com/2025/02/27/why-static-templates-make-more-sense-than-ai-driven-boilerplate-code-generation/) with Ambassador—we are pretty excited about it—not the generation, but the conversation. ;-) [Deepseek has reopened access to their API](https://techcrunch.com/2025/02/25/deepseek-reopens-access-to-its-api-after-three-week-pause/), but then [OpenAI was also signaling concerns about the impact their API has on people](https://techcrunch.com/2025/02/25/why-openai-isnt-bringing-deep-research-to-its-api-just-yet/), keeping the AI theater filled with people in the seats. In the end, I predict the future AI will be all about surveillance and policing using APIs like [Palantir](https://www.palantir.com/docs/foundry/api/v2/general/overview/introduction).

[![https://apievangelist.com/timeline/api/](https://assets.buttondown.email/images/c124bddd-eb29-434d-9056-de6478c278db.png?w=960&fit=max)](https://apievangelist.com/timeline/api/)

*The API Timeline*

[It was time to add Arrazzo, Overlays, and FAPI 2.0 to the API timeline](https://apievangelist.com/timeline/api/)—and it is always interesting to decide was is history and what is not. There was lots of nostalgia for the past with [spotting HAL and JSON-lD in the wild](https://apievangelist.com/2025/02/28/hal-and-json-ld-hypermedia-in-use-by-the-carapi/), and loving on how [curl hasn’t aged a day since 1998](https://apievangelist.com/2025/02/27/curl-and-apis/).

[![](https://assets.buttondown.email/images/9a322dff-d419-4d80-b8e8-6cf355127df5.png?w=960&fit=max)](https://apievangelist.com/2025/02/27/curl-and-apis/)

*Looking in the Mirror*

I am going to begin pivoting on the weekly knowledge building sessions this week. I’ll be taking next week off for some travel, but once I get back I am going to keep the time slots as well as the focus on fundamentals, but I am just going operate them more like office hours rather than paid workshops for a bit. I want to change up format to see if I get more people showing up. I’ll kick off the work on changing up the format this week, and begin running the new sessions the week of March 17th. I have no shortage of conversations going on, but getting them into the regularly schedule time slots is proving to be challenging, but it is essential for my sanity and budget.

*If you need API Evangelist to help out with API governance*[*please let us know how we can help*](https://apievangelist.com/contact/)*. And thank you to*[*APIMATIC*](https://bit.ly/3NyONos)*and*[*Theneo*](https://bit.ly/41n9vPS)*for their continued support. If you are interested in sponsoring our work and site please*[*review out sponsorship package*](https://partners.apievangelist.com/)*, and drop me an*[*email today*](mailto:info@apievangelist.com)*.*

***

## Discussion

No replies yet.