Discover - What did I spent to find this. I may have had to buy someone dinner or beer to find, as well as time on the Internet searching, and connecting the dots.
Negotiate - What time to I have in actually getting access to something. Most of the time its on the Internet, and other times it requires travel, and meeting with folks.
Licensing - There is a chance I would license a database from a company or institution, so I want to have this option in here. Even if this is open source, I want the license referenced as part of acquisition.
Purchase - Also the chance I may buy a database from someone outright, or pay them to put the database together, resulting in one-time fee, which Im going to call purchase.
Investment - Who put up the money to support the development of this API resource? Was it internal, or did we have to take external investment.
Grant - Was the development of this API rolled up in a grant, or specifically a grant for its development. Covering costs involved.
Normalization - What does it take me to cleanup, and normalize a dataset, or across content. This is usually he busy janitorial work necessary.
Design - What does it take me to generate a Swagger and API Blueprint, something that isnt just auto-generated, but also has the required hand polish it will require.
Database - How much work am I putting into setting up the database. A lot of this I can automate, but there is always a setup cost involved.
Server - Defining the amount of work I put into setting up, and configuring the server to run a new API, including where it goes in my overall operations plan.
Coding - How much work to I put into actually coding an API. I use the Slim PHP framework, and using automation scripts I can generate 75% of it usually, but there is always finish work.
DNS - What was the overhead in me defining, and configuring the DNS for any API, setting up endpoint domain, as well as potentially a portal to house operations.
Definition - How much resources am I applying to creating and maintaining APIs.json, Swagger, and API Blueprint definitions for my APIs.
Compute - What percentage of my AWS compute is dedicated to an API. Flat percentage of the server its one until usage history exists.
Storage - How much on disk storage am I using to operate an API? Could fluctuate from month to month, and exponentially increase for some.
Bandwidth - How much bandwidth in / out is an API using to get the job done.
Management - What percentage of API management resources is dedicated to the API. A flat percentage of API management overhead until usage history exists.
Code - What does it cost me to maintain my code samples, libraries, and SDKs for each individual API, or possibly across multiple APIs and endpoints.
Evangelism - How much energy do I put into evangelizing any single API? Did I write a blog post, or am Im buying Twitter or Google Ads? How is the word getting out?
Monitoring - What percentage of the API monitoring, testing, and performance service budget is dedicated to this API. How large is surface area for monitoring?
Security - What does it cost for me to secure a single API, as part of the larger overall operations? Does internal resource spend time, or is this a 3rd party service.
Virtualization - What am I spending on virtualization for an API, as part of QA process, for retail sandbox and simulation environments, or for specific partner needs.
API Value - Each API will have its own credit rate set, where some will be one credit, while others may be 100 credits to make a single call, it can be defined by API or a specific endpoint.
Limits - The daily allowed credit limit will be determined by the access level tier is registered at, starting with daily free public access to retail, trusted, and potentially custom tiers.
Usage - How many credits does any one user use during a day, week, or month, across all APIs. When each API is used, it will apply the defined credit value for the single API call.
Incentive - How can the platform give credits as an incentive for use, or even pay credits for writing to certain APIs, and enriching the system, or driving traffic.
Purchase - What does it cost to buy a credit, something that could fluctuate from day to day, week to week, or month to month.
Buyout - Allow API consumers to get paid for the credits on their account, preferably all users are encouraged to spend credits, but buyout is an option.
Discounts - Can we give discounts when you buy credits through specific channels, promotions, or other type of planned deal.
Volume - Are there volume discounts for buying of credits, allowing consumers to purchase credits in bulk, when they need to and apply when they desire.
Applying - Can you wait to apply credits you have accumulated? Given the option with each billing cycle to apply, or you may want to wait and use at future date.
Value - What is the value of an API resource? Often you will be just making this up, but at the least you should be able to articulate in some way.
Revenue - What revenue opportunities for the ecosystem around an API and its operation, sharing in the money made from platform operations.
Timeframes - What timeframes can be leverage to generate direct value? Timeframes should be used in conjunction with plans to dial in the value generated.
Metrics - What are the metrics, no matter what you choose to track by, what is the metric and its value? The most common metrics is the hit, but could be any other quantifiable metric you can consider.
Geo - How can geographic location be leverage as part of determining value generation? Different data centers, or networks, or possibly as part of support. How can geographic constraints be applied to maximize value generated.
Resources - The best part of API design, is you can dial in your value generate to the smallest unit of compute, the single API resource. How are APIs value generation considered at the individual level like this?
Extensions - Are there extensions available that will impact the developers, or end-users experience. Can extensions be used for a default experience, or added on to incrementally increase value generated.
Usage - How is usage wielded as part of value generation? Is value about the increased usage of a resource, or possible value generated by a minimum usage of a resource? Usage is an important dimension of determining how value is generated as part of API operations.
Fees - How are fees leveraged as part of value generation, where like usage, fees driving that value generation, or possibly the lack of fees is where the value lies. Where, within the ecosystem do discussing fees make sense?
Donations - Does API operations depend on donations, either one time, or possibly soliciting ongoing donations to make sure an API operations. An actual API may be present to allow for donations to occur in-line.
Grants - Is the value generated around API operations because of a single, or possibly multiple grants? How are grant programs leveraged to develop the API itself, or possibly drive the evolution of resources made available via APIs.
Percentages - Is value generation measured in percentages? Such as revenue share, or percentage of any resource usage for free. There are a number of ways to think about percentages, and how they apply to defining value generation.
Users - How is value generated on a per user level? More users is valuable, or possible fewer users. Teams, groups, and many other ways to determine how users impact positively or negatively the value generated from platform usage.
Relationships - How can relationships between users, or companies be applied to value generated? Will access to more relationships positively or negatively impact how value is generated for platform, and consumers?
Support - Is access to support something that impacts the value being generated? Does access to support resources introduce the optimal levels of value consumers are looking for? How is support wielded within overall platform monetization.
Applications - Is value generated looked at on a per application basis? Does having multiple applications impact the value generate? Coming up with interesting ways to understand how applications impact platform value for everyone.
Integrations - What external integrations are available? How can these be leveraged to enhance the value for consumers? Are some integrations part of base operations, where others are accessible at higher levels, or on a one off basis.
Investment - Similar to donations, what investment possibilities are part of platform operations? How can access to invest be a value option for consumers, and be used to create more value for platform operators?
Marketing Vehicle - Having an API is cool these days, and some APIs are worth just having for the PR value, and extending the overall brand of the platform.
Traffic Generation - The API exists solely for distributing links to web and mobile applications, driving traffic to specific properties - is this tracked as part of other analytics?
Brand Awareness - Applying a brand strategy, and using the API to incentivize publishers to extend the reach of the brand and ultimately the platform - can we quantify this?
Data & Content Acquisition - Using the API, and the applications built on top as part of a larger data and content acquisition strategy--can we quantify this?
SaaS - Value generated is focused on SaaS services, and API value generation is about augmenting these services, secondary to the core SaaS business model.
PaaS - Value generated is focused on PaaS services, and API value generation is about augmenting these services, secondary to the core PaaS business model.
Devices - An API exists purely in support of a device, such as Fitbit, or with a 3D Robotics Drone. All value generated by the API is about enhancing, and building on the overall device experience.
Products - An API exists in support of a specific product. Just like devices, but products could be physical devices that are not connected to the database.
Services - As with products, an API may exist to augment an existing in-person, or possibly a digital service being offered by a company. The API value is centered around this service, and not the actual API.
Syndication - An API exists to help syndicate data or content on the web. All value generated by the API is in service of the syndication process.
Analytics - How can analytics be leveraged as part of API value generation? Are analytics part of the base of operations, or are they an added value incentive for consumers, and platform operators.
Reporting - How is reporting via an API platform part over the overall value being generated? Reporting can be something that benefits internal or external operators, and bring more value to the table.
Talent - How is talent, from an HR perspective considered as part of the value being generated by an API? Does the API exists as a sort of honeypot to attract talent for hire, project work, or possibly acquisitions and investments.
Security - How is security used as a lens for measuring, quantifying, and delivering value via the platform. Does the existence of security only available at higher levels or on-demand usage? Security will continue to play an ever increasing role in API monetization.
Partner Revenue Generation
Link Affiliate - What revenue is generated and paid out via links that are made available via the API, with potentially externally affiliate links embedded.
Revenue Share - What portion API revenue is paid out to potential re-sellers who drive API usage. Revenue is percentage of overall credit purchases / usage.
Credits to Bill - All revenue is paid in credits on account, and user can decide to get buy out of credits at any time, or possibly use in other aspects of system operation.
Reseller - Is there a reseller program available for any levels of API platform operations? Are API consumers incentivized to sell products or services, in which they are compensated for? How can platform value being broken up using reseller approaches?
Timeframe - How much revenue is being brought in on a daily, weekly, monthly, quarterly, or annual basis for an API and all of its endpoints.
Users - How much revenue is being brought in on a monthly basis for a specific user, for an API and all of its endpoints.
Applications - How much revenue is being brought in on a monthly basis for a specific application, for an API and all of its endpoints.
Plans - Which plans generate most usage and revenue? I should be applying just as easily to aspects of platform / internal usage as well. Better understanding value generated across all plan levels.
Affiliate Revenue - What was generated from affiliate links made available via APIs, minus what percentage was paid out to API consumers.
Advertising Revenue - What advertising revenue was derived from web or mobile application traffic resulting from the API, minus whatever was paid out as rev share to API consumers.
Country - How are things broken down by country? Country defined API operations will continue to be an important way to look at API operations, and value generated.
Region - Keeping in alignment with traditional sales regions, and looking at value generated within specific regions.
Add-Ons - Are add-ons used to monetize the platforms? Are they a unit of value that can be used as part of base operations, or on-demand, or as part of any other dimension of API plans?
Reciprocity - How can API interoperability, automation, and reciprocity with other platforms be used as part of the overall API monetization strategy? Common approaches to reciprocityi can be leveraged as part of API monetization and planning.
Single Sign On (SSO) - How can Single Sign On be leveraged as part of API monetization? Are there some opportunities that can be available for free, or are there other higher levels of access where SSO is an option? Consider how this level of authentication can impact monetization?