Grapevine is an accountless API for publishing data with built-in pricing. A lot of useful information never finds a market. Grapevine makes it easy to package data and let people or systems request and pay for it directly.
The core idea is that pricing and payment happen inside the request using Coinbase’s x402 flow. No accounts, no onboarding steps, no checkout. A buyer signs the request, pays, and receives the data in one call. It behaves more like an authenticated API request than a marketplace.
Content is organized into feeds and entries. A feed is an ongoing source of data. An entry is a single item such as text, a file, a dataset, or any other type of content. Each entry can have its own price, so one-off pieces of information work just as well as larger collections.
Data is stored using private IPFS, which provides a verifiable CID for each entry while keeping the content private.
We’ve thought a lot about this over the last few years. IPFS is the standard for content verifiability of NFTs. Can you prove that the content is what the original creator said it was? That's what IPFS solves for better than anything else. Watch this video to learn why: https://youtu.be/vttw1bjC2no?t=478
With IPFS solving content verifiability for NFTs first, you then have to solve for who is responsible for the NFT data. Decentralized storage doesn't inherently solve for this. Someone still needs to pay for it and this creates massive friction. We discuss this problem here: https://medium.com/pinata/who-is-responsible-for-nft-data-99...
Ultimately, the person who cares most about an NFT is the person who currently owns it. Whether that is the platform, the creator, or the collector, enabling them to easily ensure their NFTs survive ownership changes is going to be crucial to the success of NFTs long-term.
The core idea is that pricing and payment happen inside the request using Coinbase’s x402 flow. No accounts, no onboarding steps, no checkout. A buyer signs the request, pays, and receives the data in one call. It behaves more like an authenticated API request than a marketplace.
Content is organized into feeds and entries. A feed is an ongoing source of data. An entry is a single item such as text, a file, a dataset, or any other type of content. Each entry can have its own price, so one-off pieces of information work just as well as larger collections.
Data is stored using private IPFS, which provides a verifiable CID for each entry while keeping the content private.
Docs: https://docs.grapevine.fyi
App: https://www.grapevine.fyi
Code: https://github.com/PinataCloud/grapevine