3 ms·

I am really sorry, but looking at your website, I did not understand what's the purpose of your company. Reading up your comment, it does not make much more sen

I am really sorry, but looking at your website, I did not understand what's the purpose of your company. Reading up your comment, it does not make much more sense to me. Are you somehow like snipcart?

RileyJames 6y ago
From reading through their site it seems to replace affiliate links with api calls. Ie: I have a website (Channel), rather than place affiliate links, I can request products from an api and sell them directly to my users (audience). Makes more sense when the channel is not a website (ie something that doesn’t have links) like a instagram story, or virtual environment. You want to sell the latest console / game from Microsoft, they provide an api, you pull the trailer, screenshot (media) and a price. The user can click buy there and then, you take payment via stripe and send an order to Microsoft via the api. Microsoft then fulfils the order. Somewhere between affiliate and retailer.
rhenzabel 6y ago
What @RileyJames said is spot on. When you think about it outside of the lens of websites, it starts to become more clear. Our thesis is that apps should be able to sell natively, without any form of clickouts to external websites, which is how traditional affiliate links operate today. We believe that transactions should be able to occur natively in any environment that has an internet connection. If commerce is ever to occur in environments like games, voice, VR, etc; clickouts would likely be impractical, and a headless API would be needed to facilitate the transaction. This headless API is what we've been working on. We essentially integrate with all of the ecom platforms (think BigCommerce, Magento, Shopify, etc) and normalize their catalog and checkout/order API's into this single headless API. Developers can then integrate with this single API, and gain access to the products in our system, which are sourced from merchants on all of those platforms. Developers can then add native checkout (no clickout) to their apps, and earn a commission (defined by the merchant) for each order they facilitate. These orders are written back directly into the merchants existing tools, where the order appears as if it had been placed on their website. Also, I do agree that our landing page can be pretty confusing. We're serving a double-sided marketplace and are still working on finding that right language that makes sense to both sides.

RileyJames 6y ago

From reading through their site it seems to replace affiliate links with api calls. Ie: I have a website (Channel), rather than place affiliate links, I can request products from an api and sell them directly to my users (audience). Makes more sense when the channel is not a website (ie something that doesn’t have links) like a instagram story, or virtual environment. You want to sell the latest console / game from Microsoft, they provide an api, you pull the trailer, screenshot (media) and a price. The user can click buy there and then, you take payment via stripe and send an order to Microsoft via the api. Microsoft then fulfils the order. Somewhere between affiliate and retailer.

rhenzabel 6y ago

What @RileyJames said is spot on. When you think about it outside of the lens of websites, it starts to become more clear. Our thesis is that apps should be able to sell natively, without any form of clickouts to external websites, which is how traditional affiliate links operate today. We believe that transactions should be able to occur natively in any environment that has an internet connection. If commerce is ever to occur in environments like games, voice, VR, etc; clickouts would likely be impractical, and a headless API would be needed to facilitate the transaction. This headless API is what we've been working on. We essentially integrate with all of the ecom platforms (think BigCommerce, Magento, Shopify, etc) and normalize their catalog and checkout/order API's into this single headless API. Developers can then integrate with this single API, and gain access to the products in our system, which are sourced from merchants on all of those platforms. Developers can then add native checkout (no clickout) to their apps, and earn a commission (defined by the merchant) for each order they facilitate. These orders are written back directly into the merchants existing tools, where the order appears as if it had been placed on their website. Also, I do agree that our landing page can be pretty confusing. We're serving a double-sided marketplace and are still working on finding that right language that makes sense to both sides.