> For the complete documentation index, see [llms.txt](https://docs.cdpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdpi.dev/technical-notes/digital-payment-networks/discovery-and-fulfillment-networks/platforms-to-protocols.md).

# Platforms to Protocols

*Consider this: Buber is the leading ride-hailing app in country A. Buber takes a huge commission from the drivers and also charges the passenger unfairly. Still, both parties are left with no choice but to use Buber due to strong network effects from the aggregation of a large number of drivers and passengers, creating a virtual monopoly. Sounds familiar? Read on!*

With every passing day, more and more services are becoming digital, often powered by private platforms that have disrupted traditional service providers. A consistent pattern has emerged: strong network effects lead to data concentration among a few large players. Closed-loop marketplaces have become the norm. Apps are not interoperable, and all individual businesses have to solve all parts of the transaction cycle: **discovery, ordering, fulfillment, and post-fulfillment**.

While an aggregator-led model (where both service providers and end users are onboarded to the same platform) appears to work efficiently, it does not scale beyond a point. Besides, large aggregators often adopt business policies that are advantageous to neither the service provider nor the end user.

Data in siloes, predatory monopolistic practices, lack of scale, and exclusion of certain population segments all indicate a need to shift the approach from “platform” to “networks”. Imagine trusted, low-cost, decentralized transactions at scale. This is what open networks aim to achieve!

**Reference:**

1\. <https://becknprotocol.io/><br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cdpi.dev/technical-notes/digital-payment-networks/discovery-and-fulfillment-networks/platforms-to-protocols.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.