Project Name
API key Sharing
Project Category
Outreach
Proposal Earmark
New Outreach
Proposal Description
API Key Sharing
APIs allow users to access a variety of curated information, allowing for connecting applications to new streams of data. Despite these advantages, API’s are not easy to obtain, and can be expensive, especially if there is monopoly power (twitter). This promotes API providers to lock-in their clients without much concern for what is best for the user. This is why we believe that once a client buys access with an API, they should be able to sell it without the provider having any control on such autonomy. We believe that ocean’s data assets can be repurposed to storing API keys for Users. This would involve having an API key’s URI be stored in the DDO metadata, after being encrypted by the provider. This allows owners of the key to monetize, share and bundle API keys.
API Bundles
API bundles involve a set of users bundling their API keys into a single Data Asset. This would be done by having multiple URI’s representing each of the keys. The additional Information field will then have a mapping between each uri and the API metadata for consumers know which uri belongs to which API. This allows for users to create assets that bundle API keys into one access point, which can be a compelling commodity for users who do not want to subscribe to each key.
Monetizing Your Own Endpoint
Allowing ocean to handle APIs empowers developers to monetize from their own endpoints they create. This promotes a peer to peer economy of API’s, avoiding third party sellers and lockins.
Grant Deliverables
- Selling there API keys as data-asset
- Having a data asset represent a bundle of API keys
Project Description
API Key Sharing
APIs allow users to access a variety of curated information, allowing for connecting applications to new streams of data. Despite these advantages, API’s are not easy to obtain, and can be expensive, especially if there is monopoly power (twitter). This promotes API providers to lock-in their clients without much concern for what is best for the user. This is why we believe that once a client buys access with an API, they should be able to sell it without the provider having any control on such autonomy. We believe that ocean’s data assets can be repurposed to storing API keys for Users. This would involve having an API key’s URI be stored in the DDO metadata, after being encrypted by the provider. This allows owners of the key to monetize, share and bundle API keys.
API Bundles
API bundles involve a set of users bundling their API keys into a single Data Asset. This would be done by having multiple URI’s representing each of the keys. The additional Information field will then have a mapping between each uri and the API metadata for consumers know which uri belongs to which API. This allows for users to create assets that bundle API keys into one access point, which can be a compelling commodity for users who do not want to subscribe to each key.
Monetizing Your Own Endpoint
Allowing ocean to handle APIs empowers developers to monetize from their own endpoints they create. This promotes a peer to peer economy of API’s, avoiding third party sellers and lockins.
Final Product
The final product would be a simple example of a user account gaining access to an api key via a data NFT. The API key would be stored in IPFS and will allow the user to decrypt the cid when the condition is met.
Value Add Criteria
Allowing developers to share and privatize there own custom API's, this adds a new utility of sharing assets that fall outside of typical datasets. As a result the ocean community can attract new members that rely on sharing and monetizing APIs.
Core Team
Salvatore Vivona
Role: Software Engineer, AI engineer
Relevant Credentials:
LinkedIn: https://www.linkedin.com/in/salvivona
Github: salvivona · GitHub, commune ai · GitHub
Advisors
Funding Requested
3000
Minimum Funding Requested
3000
Wallet Address
0x9C73542592BB3534Fa0C847580043b3563D1161b