# Ecosystem Partners & Integration Providers ### **Plug in once, reach everyone.** Integrating with City Protocol means your service (yield, swaps, lending, payments, KYC) reaches every project and user connected to the SDK. Instead of negotiating partnerships one by one, plug into a single infrastructure layer and gain access to the full network of vault operators, depositors, and developers building on the platform. *** ### **Native embedding, not peripheral listing.** Partners aren't bolted on as optional extras. They're woven into the module architecture. When a curator rebalances, the Swap Module routes through integrated DEXs natively. When a user on-ramps fiat, the Ramp Module dynamically selects the best gateway for their jurisdiction. When a vault requires KYC gating, the Whitelist Manager connects directly to the integrated identity provider. You see real usage, not just a logo on a docs page. *** ### **Performance-based volume routing.** The Ramp Module routes transactions to the provider with the highest authorization rates and lowest fees for the user's specific jurisdiction and payment method. The Swap Module aggregates liquidity for best-execution pricing and minimal slippage. Competitive performance translates directly into higher volume allocation. It's a merit-based system, not a static integration list. *** ### **Exposure to the attention-capital flywheel.** City Protocol sits at the intersection of user acquisition (Viral City, AaaS) and financial infrastructure (NaaS). Partners don't just get capital flow exposure. They get amplified by the attention economy layer feeding those flows. A yield provider benefits when a Viral City campaign brings in new depositors. A payment gateway benefits when reward distributions trigger ramp activity. The flywheel amplifies partner usage beyond what a standalone integration would deliver. --- # Agent Instructions: 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: ``` GET https://city-protocol.gitbook.io/docs/introduction/value-proposition/ecosystem-partners-and-integration-providers.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.