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!
blog comments powered by Disqus
Latest Blog Posts
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government
- After Last Couple of Weeks, It's Clear There Is Big Opportunity In The API Space