# Marketplaces Published articles for Marketplaces. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## API Marketplaces and the Invisible Economy: Trade Routes of the AI Era DevFeed: [API Marketplaces and the Invisible Economy: Trade Routes of the AI Era]() Original publisher: [Read original article]() Author: Chris Darvill Published: 2026-08-04T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Artificial Intelligence](), [Orchestration]() Tags: [ai-agents](), [api](), [api-as-a-product](), [api-business-models](), [api-discovery](), [api-economy](), [api-ecosystem](), [api-governance](), [api-management](), [api-monetization](), [apis](), [artificial-intelligence](), [blog](), [governance](), [marketplaces](), [monetization](), [orchestration](), [strategy]() ### AI overview The article explains how API marketplaces can turn APIs into tradable services for AI agents, supporting monetization, governance, and orchestration. ### Source excerpt APIs are like the backstage crew of the digital economy. They're not front and center, but they're essential for putting on a show. Yet, from a business perspective, APIs have traditionally been regarded as a form of "operational plumbing," with many enterprises treating them as technical infrastructure rather than strategic assets. However, companies like Stripe, ... ## DAC7 Reporting: A Practical Guide for Platform Operators DevFeed: [DAC7 Reporting: A Practical Guide for Platform Operators]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-07-31T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [data](), [XML]() Tags: [compliance](), [data](), [eu](), [guide](), [identity](), [marketplaces](), [platform](), [tax]() ### AI overview A practical guide to DAC7 reporting for digital platform operators, covering scope, seller due diligence, required identity and earnings data, annual reporting obligations, exclusions, deadlines, and the effect of a merchant-of-record arrangement. ### Source excerpt What DAC7 reporting requires from platforms: who must report, which activities are in scope, the seller data to collect, and the 31 January deadline. ## Treating Pricing Changes Like Code Deploys DevFeed: [Treating Pricing Changes Like Code Deploys]() Original publisher: [Read original article]() Author: Ananda Kanagaraj Sankar Published: 2026-07-22T18:09:48Z Content type: article Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [Deployment](), [DynamoDB](), [Go Language](), [Code review]() Tags: [code-review](), [deployment](), [devops](), [dry-run](), [dynamodb](), [engineering](), [go](), [marketplaces](), [monitor](), [platform-engineering](), [pricing-strategy]() ### AI overview This article explains how Thumbtack handled large pricing changes by comparing them with code deployments. Pricing bids stored in DynamoDB were rewritten in bulk using custom Go scripts, but those scripts lacked built-in resumability, runtime control, and durable records for undoing changes. ### Source excerpt Making large pricing changes safe to run, safe to resume, and safe to undo. Most days, shipping code to production at Thumbtack is a non-event. You merge your change, a deployment pipeline takes it from there and it rolls out while you monitor the rollout. If a deploy stalls, the system already knows which step it stalled on. If it goes wrong, rolling back is a button away. It's the return on years of platform work, so routine now that we mostly forget it's there. Which is the point: Safety is built into the road, not into how carefully each person drives. Changing pricing data never had that platform at Thumbtack. Pricing is how a marketplace like ours sustains itself. It lets us capture a share of the value we help create, and it's something we tune on an ongoing basis rather than set once. We test pricing changes, measure their impact and roll out the ones that work. Mechanically, this runs on an auction. When a customer creates a project on Thumbtack, pros compete for the lead, and what a pro is willing to pay shows up as a bid. Those bids are stored per pro's service offering (a specific offering a pro provides, like house cleaning or landscaping) as bid settings in DynamoDB. Rolling out a pricing change means rewriting those settings in bulk, often a few hundred thousand of them at a time, several times a year. For a long time, each of the pricing rollouts was a custom Go script written for that specific change. The scripts were production grade. They went through code review, ran in staging first, did a dry run before any live write, and were rolled out in stages. That was a reasonable way to work: the changes are infrequent, each one is genuinely different from the last, and a script you can read top to bottom is easy to trust. But what reviews and a good runbook can't give you is the runtime machinery. A script doesn't remember where it was when it died, so it can't safely pick up where it left off. It has no real sense of how hard it's pushing the database ## Variance Reduction Below the Randomization Grain DevFeed: [Variance Reduction Below the Randomization Grain]() Original publisher: [Read original article]() Author: Tilman Drerup Published: 2026-07-01T16:28:36Z Content type: article Language: en Sources: [Instacart]() Topics: [experiments]() Tags: [capacity](), [causal-inference](), [economics](), [engineering](), [experiment](), [experimentation](), [experiments](), [machine-learning](), [marketplaces](), [metrics](), [reduce](), [science](), [techniques](), [variance]() ### AI overview This article explains how marketplace experiments can reduce metric variance below the level at which treatment is randomized. It describes cluster-level randomization for containing interference and shows how fine-grained outcome predictability can improve statistical power and reduce experimentation time. ### Source excerpt Sergio Camelo, Caitlin Kearns, Matias Cersosimo, and Tilman Drerup As artificial intelligence increases the velocity of engineering and science teams, experimental throughput is set to become a bottleneck for many product decisions. Many companies can now build faster than they can experiment, with queues of good ideas running the risk of not being tested because of lack of experimental capacity. This problem is particularly severe in marketplaces, where the presence of spillover and cannibalization effects between experimental units requires cluster-level randomization techniques. That randomization, in turn, has the unfortunate tendency to substantially reduce statistical power and slow down experimentation. In this post, we show that the predictability of outcomes at fine grains can be exploited to reduce the variance of aggregate metrics, even when experiments themselves are run at a coarse level. Since statistical power depends on metric variability, this yields considerable reductions in experimentation time. The Interference Problem In marketplace settings, behavior and outcomes for individual participants are inherently intertwined. In a delivery marketplace like Instacart, for example, the dispatch system solves a bipartite matching problem between shoppers and customer orders. Since assignments are global and interdependent, matching an order to one shopper means that the same order cannot be matched to another shopper. As a result, changing the handling for a single order creates ripples that affect the orders around it. If an experimenter were to assign a treatment intervention to one of these orders while leaving neighboring orders as controls, the latter would evidently be contaminated. A common response to this problem is to randomize treatments at the level of a cluster, chosen so that interference can stay within it. In food and grocery delivery, that cluster is typically a geographical region. Since every order within a region sees the same treatme ## Stripe Connect Alternatives for Marketplace Payments DevFeed: [Stripe Connect Alternatives for Marketplace Payments]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-14T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [stripe](), [Transactions]() Tags: [alternatives](), [chargebacks](), [compare](), [complexity](), [compliance](), [fees](), [guide](), [integration](), [legal](), [marketplaces](), [merchant-of-record](), [onboarding](), [payments](), [platforms](), [pricing](), [regulatory](), [reporting](), [requirements](), [saas](), [stripe]() ### AI overview A guide to alternatives to Stripe Connect for marketplace payments. It compares approaches for split payments, seller onboarding, payouts, compliance, currencies, and pricing, including Dodo Payments' merchant-of-record model. ### Source excerpt Looking for Stripe Connect alternatives? Compare marketplace payment platforms that handle split payments, seller onboarding, and multi-party payouts. ## White Label Payment Gateway: What It Is and Who Needs One DevFeed: [White Label Payment Gateway: What It Is and Who Needs One]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [API](), [Software](), [User experience (UX)]() Tags: [api](), [checkout](), [compliance](), [core](), [embedded-finance](), [gateway](), [integration](), [marketplaces](), [merchant-of-record](), [monetization](), [payment-gateway](), [payments](), [platforms](), [product](), [saas](), [ux]() ### AI overview This guide explains what a white label payment gateway is, which platforms may need one, what it does not solve, and how to evaluate branding, control, compliance, and integration tradeoffs. It distinguishes branded checkout and embedded payments from deeper payment facilitation and Merchant of Record requirements. ### Source excerpt Learn what a white label payment gateway is, when platforms need one, and how to evaluate branding, control, compliance, and integration tradeoffs. ## How to Sell WordPress Plugins and Themes: The Complete 2026 Guide DevFeed: [How to Sell WordPress Plugins and Themes: The Complete 2026 Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-06T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [WordPress themes and plugins](), [WordPress Plugins](), [WordPress](), [Support]() Tags: [2026](), [digital-products](), [guide](), [how-to](), [marketplaces](), [monetization](), [payment](), [payment-processing](), [plugins](), [pricing](), [product](), [themes](), [wordpress]() ### AI overview A practical 2026 guide to selling WordPress plugins and themes. It covers licensing, pricing, updates, support, payment processing, and the trade-offs between marketplaces and direct sales, including WordPress.org and Envato Market. ### Source excerpt Learn how to sell WordPress plugins and themes online with the right licensing, pricing, delivery, and payment setup - without marketplace commissions. ## How to Build a Marketplace for Digital Products DevFeed: [How to Build a Marketplace for Digital Products]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software](), [coding](), [API]() Tags: [architecture](), [building](), [digital-products](), [how-to](), [infrastructure](), [management](), [marketplaces](), [payments](), [platform](), [saas](), [tax](), [technical]() ### AI overview A practical guide to building a multi-vendor marketplace for digital products. It covers vendor management, product catalogs, payment flows, commissions, automated delivery, entitlement management, and global tax compliance, including how Dodo Payments can provide financial infrastructure and API-based product management. ### Source excerpt Launch your own multi-vendor marketplace for digital goods. Learn how to handle payments, commissions, and global tax compliance with Dodo Payments. ## Backwards Incompatible V2 API Changes DevFeed: [Backwards Incompatible V2 API Changes]() Original publisher: [Read original article]() Author: Benjamin Dean Published: 2020-04-03T00:20:55Z Content type: release Language: en Sources: [Zoom Developer Blog - Medium]() Topics: [REST API](), [zoom](), [API](), [passwords]() Tags: [api](), [developer](), [marketplaces](), [password](), [release](), [rest-api](), [zoom]() ### AI overview Zoom announces backwards-incompatible V2 REST API changes following the removal of Attention Tracking. The affected fields return empty or false values, and some password-related settings become immutable for certain K-12 Education accounts. ### Source excerpt In accordance with the removal of the Attention Tracking feature in Zoom, we have made the following breaking changes to the V2 REST API effective upon the release April 3rd, 2020: Deprecating "attentiveness_score" field in Meeting, Webinar Participants Report APIs. The API Responses to your requests on the following APIs will always return an empty value for the ("attentiveness_score") field. GET /v2/report/meetings/{meetingId}/participants GET /v2/report/webinars/{webinarId}/participants 2. Deprecating "attention_tracking" field in User, Group, and Account APIs. The API Responses to your GET requests on the following APIs will always return a "false" value. GET /v2/accounts/{accountId}/settings PATCH /v2/accounts/{accountId}/settings GET /v2/accounts/{accountId}/lock_settings PATCH /v2/accounts/{accountId}/lock_settings GET /v2/groups/{groupId}/settings PATCH /v2/groups/{groupId}/settings GET /v2/groups/{groupId}/lock_settings PATCH /v2/groups/{groupId}/lock_settings GET /v2/users/{userId}/settings PATCH /v2/users/{userId}/settings We will continue to present the fields listed above in the API responses for the time being, but responses for these fields will return either an empty value or "false", as indicated above. In a TBD future release, we will remove these two fields entirely. 3. Beginning April 12th, 2020, password-related settings can no longer be modified (immutable, always returning TRUE) for K-12 Education accounts that are Free or Pro (single host). These password-related settings are enabled by default, and can be changed by the owner/admin on: free accounts, or Pro accounts (with only one single host license). NOTE: Free Accounts with CC are permitted to adjust this setting. The above changes are relevant for the following fields of the given APIs: The "require_password_for_scheduling_new_meetings" field, "require_password_for_instant_meetings" field, and "require_password_for_pmi_meetings") field on these APIs: GET /v2/accounts/{accountId}/settings