Posted on 03-15-2013
Maciej Ceglowskiis, the founder of popular social bookmarking platform Pinboard,made an interesting proposal over on the Pinboard Google Group:
I've been thinking about imposing an API tax, the proceeds of which would go into improving API infrastructure and offsetting operating costs, structured along these lines:
- API free to use for your own Pinboard account
- Every API client making requests on behalf of someone else must register an app identifier
- $20/year tax if your app makes requests for over 100 Pinboard accounts
- $100/year tax if your app makes requests for over 1000 Pinboard accounts
- Possibly additional price levels to waive certain rate limits
Think of it as a road tax that then pays for further construction, repair, and people in orange vests.
I’m guessing that Maciej has a lot of experience to back his proposal, watching how developers use Pinboard for their own purposes, or on behalf of a user via a client. I heavily depend on Pinboard for my curation at API Evangelist, so API access would remain free for me. I’m not sure how I would feel if I was building a client.
On the forum, there is very interesting feedback from Matt Schmidt, developer of PinDroid, the leading Pinboard client for Android:
I'm very much against this. Why would you tax the makers of the apps that help drive use of your product, rather than the users themselves? To extend your road use tax analogy, this is like taxing the car companies for their customer's use of the roads.
I offer PinDroid as a free, open source app and have no interest in making money off it, but I also have no interest in losing money on it. Why not offer api access as a premium account feature (like archiving) for an extra buck instead?
To be clear, if such a "tax" were to be implemented, I will have to stop developing and supporting PinDroid and take it off the market.
Matt provides some real life feedback, that I can’t. PindDroid is a vital player in the PinBoard ecosystem, that could be hurt by such a tax. Free and open source code and clients are a vital aspect of any API ecosystem, you definitely want to understand how this layer will be affected by such a tax.
Maciej just made this proposal today, so the conversation is fresh. Head over to the Pinboard Google Group to weigh in. I’ll post another story after the conversation dies down, providing more thoughts about API taxes.
Thanks Marsh (@earth2marsh) for alerting me to the conversation!
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
- A Mobile Developer Toolkit With The University Of Michigan APIs
- Kicking Off Image Manipulation API Work