Should government charge API fees?

There’s a new topic posted on the US Government APIs Google group inquiring about instances of government agencies using pay models for government APIs.

My default answer to this is no, that we should treat it much like we do other public goods. Just like any venture, government agencies need to reconfigure their budgets and IT operations to provide a public API offering.

In this day and age, government needs to take into account that data and APIs are a twenty-first century public offering. If agencies are trying to justify data/APIs from a budgetary perspective, the first step would be to reallocate funding priorities and eliminate antiquated services these offerings replace.

Pay for the data, streamline IT processes that make it easier and cheaper to publish data, eliminate outdated operations they replace and empower third-parties to leverage that data and provide more market-based public services. If we’re going to start charging for data/APIs, we need to first do a holistic assessment of what the ecosystem looks like if we’re going to innovate our thinking around it, as opposed to looking at it from a micro perspective.

I can see in high-usage cases where there may be some merit to charging for data usage, but we’re still a long ways away from that discussion. Let’s innovate first before jumping into pay-for-use fees.

Would love to hear other opinions on this. Share your thoughts.

About Luke Fretwell

Luke Fretwell is the founder of GovFresh and a strategy consultant for CivicActions and NuCivic. He can be reached at luke@govfresh.com.

2 Responses

  1. I don’t think it would be a bad idea to charge a flat fee for businesses that leverage APIs on a large scale. I believe government sponsored APIS would be better served if they took a lesson from the opensource community and leveraged crowd sourcing. There are many people (myself included) that would help make these data sources more readily available.

Comment