# How Thesauros fits your product A customer experience, an integration API and a capital layer—with clear responsibilities between them. Thesauros brings yield infrastructure into the products where customers already hold stablecoins. The integration connects three distinct responsibilities: the customer journey, the data your backend operates on, and the contracts that hold and allocate assets. ## Your product experience You choose where Earn lives, how the customer enters it, and how balances and activity are presented. Your product also defines the customer identity, account model and support journey. Your backend holds the API credentials. It maps your customer IDs to attributed users and sends the relevant data to the interface without exposing partner secrets. ## The Partner API The Partner API is a NestJS service backed by PostgreSQL. It provides partner and campaign records, user attribution, protocol yield history, partner-scoped activity, revenue calculations, webhooks, usage and reconciliation. Its methods are an integration and reporting surface. The contract does not expose a general-purpose endpoint that signs a customer transaction or creates a real onchain position. Transaction construction, signing and deployment details form a separate part of your launch configuration. ## The vault and allocation layer The protocol materials describe vaults, strategies and adapters for underlying lending markets. A vault represents the asset position; strategy and adapter logic connect it to the approved market configuration. The integration must identify the actual vault, network, asset, role assignments and applicable contract version. Review the [vault model](/concepts/vaults/) and [deployment handoff](/security/deployments/) together. ## The developer console and sandbox The developer console is a separate Next.js application. It contains a working sandbox API and can also display data through configured Partner API and monitoring proxies. The sandbox implements a simulated Earn lifecycle. It is useful for experience design and integration experiments because positions, balances and activity can be exercised without a wallet transaction. ## The data boundary | Data | What it tells you | What it does not establish | | --- | --- | --- | | Protocol APY history | Recorded rates for an asset across the configured vault data | A particular customer's realized return | | Partner attribution | Which users and records belong to a partner | The identity or ownership of an arbitrary wallet | | Partner revenue response | A calculation based on balances, rates and fee assumptions | A settled payout | | Reconciliation report | Whether compared records agree, differ or are unavailable | Agreement when an upstream source could not be read | | Sandbox position | The simulated lifecycle and response shape | A blockchain deposit | These boundaries keep the customer experience clear and give engineers a reliable basis for [building and operating the integration](/operate/launch/).