> ## Documentation Index > Fetch the complete documentation index at: https://docs.powerhq.co/llms.txt > Use this file to discover all available pages before exploring further. # Choose your integration > The Drop-in Storefront puts our shopping experience on your site in days. The Plan Data API lets you build your own. Compare what you build, what you keep, and what each one costs you. Two ways to put energy shopping in front of your customers, and how to pick without a developer in the room. They differ in one thing: **how much of the shopping experience you want to own, and keep owning.** Everything behind the checkout is identical either way. Same suppliers, same plans, same enrollment, same compliance work. And neither one costs you anything: PowerHQ pays you for the customers you send, not the other way around. **Unless you have a specific reason to build your own interface, start with the Drop-in Storefront.** It puts our shopping experience on your site, under your brand, in days, with nothing for anyone on your side to build. | | Drop-in Storefront Recommended | Plan Data API | | ------------------------------ | ---------------------------------------------------------------------------------- | --------------------------- | | **What it is** | Our shopping experience, running on your site | Plan data you build with | | **What you build** | Nothing | Your own shopping interface | | **Developer needed** | No. One line of HTML, pasted once | Yes, and ongoing | | **Where customers shop** | On your site | Inside your product | | **Whose brand** | Yours, with a small Powered by PowerHQ badge | Entirely yours | | **Who keeps it converting** | We do | You do | | **New features** | Appear automatically | You build each one | | **Ongoing maintenance** | None | Yours | | **Time to live** | Days | Weeks, then ongoing | | **Checkout and customer data** | PowerHQ | PowerHQ | | **What it costs you** | Nothing. We pay you. | Nothing. We pay you. | **Looking for something even simpler, or don't have a website?** You can take a plain affiliate link instead. Same shopping experience, same compensation, hosted on PowerHQ rather than embedded in your site, and there is no page required to put it on. Ask your partner manager for one. You are not locked in. Partners commonly launch on the Storefront to prove the channel converts, then move to the API later if energy earns a permanent place in the product. Nothing about starting simple closes a door. ## Drop-in Storefront **Our shopping experience, running on your site, under your brand. We hold the supplier contracts.** Your visitors compare plans, choose one, and complete enrollment without ever leaving your site. To them it is your page. Behind it, it is the same shopping experience we run and refine every day. ### What it actually takes to set up One line of HTML, on the page where you want it, the same way a YouTube video or a Google Map goes on a page. Whoever looks after your website pastes it in once. Nothing to build, nothing to maintain, no developer required on your side. That is the whole technical lift. Most of onboarding is us configuring your branding and your tracking codes, not you doing work. ### Your brand, described honestly Your fonts, your colors, your page, and confirmation emails that go out under your name. PowerHQ stays visible in exactly two places: a small Powered by PowerHQ badge, and the disclosures your state requires. That badge earns its space. At the moment a shopper is deciding whether to hand over an account number, it shows a licensed energy provider stands behind the transaction, which is reassurance you would otherwise have to build from scratch. ### What you get without lifting a finger * **Every market, one embed.** The experience recognizes the customer's market automatically. You do not maintain a version per state. * **Residential and business by default.** Or point a specific placement at just one, so your commercial pages show business plans only. * **Your look.** Your fonts and colors, and customer emails that carry your name. * **A head start when you have one.** If you already know the customer's ZIP code, pass it in and they land straight on their plan results instead of typing it again. ### It gets better without you scheduling anything This is the same shopping experience we run for our own customers, so we are testing and improving it constantly. When we make it better, your storefront gets better. No project, no release to wait for, no work on your end. That is the part that is easy to underrate on day one and hard to ignore a year in. Partners who build their own interface only get an improvement when they build it themselves. **Best when** you want energy live on your own site in days, and the shopping experience is not where you want to spend engineering time. For most partners, that is the whole story. Working with a developer? The [Storefront reference](/storefront) has the full link structure, every parameter, sizing, ZIP pre-loading and the reports you get. Onboarding asks for the IP addresses your team will be testing from so we can enable your test links. Branding, customer types and test links. Typically live in days, not months. ## Plan Data API **You render the plans. We run everything behind checkout.** A single GraphQL endpoint returns residential and business plans for any deregulated ZIP code, with component-level pricing, supplier scores, disclosure documents and a ready-to-use enrollment URL per plan. You build the interface exactly as you want it. When the customer picks a plan, you hand them to the PowerHQ-hosted checkout and we take it from there: contract, eSign, credit, fulfillment. One endpoint, always `POST`, your key in the `x-api-key` header. Ask for exactly the fields you need and get back just those. **Best when** the energy experience has to live natively inside a product you already maintain. You have a product team, a design system, and a reason to rank or filter plans against data you already hold about the customer. It is the right call for software companies making energy a permanent part of what they sell, and it is the one path with no PowerHQ badge anywhere. Worth being clear-eyed about the commitment: the interface is yours to build, and then yours to keep optimizing. Conversion improvements we make to the Storefront do not carry over to an interface you built. Plenty of partners take that trade deliberately. It should be deliberate. Real queries against live production data, right now. Your first working call, then the full query reference. Keys, environments, the plan-display accuracy review, and going live. ## What both paths have in common * **PowerHQ owns the regulated parts.** Supplier contracts, licensing, state-by-state compliance, enrollment operations and customer service. * **Checkout is hosted by PowerHQ**, so payment and personal data never land in your systems. * **Every deregulated market**, residential and business, from one integration. * **You never pay PowerHQ.** No setup fee, no license, no monthly minimum. We pay you for every customer who enrolls, and your rates are set in Exhibit A of your partner agreement. ## Still deciding? The honest shortcut: the Drop-in Storefront is live in days, costs you no engineering time, and is the experience we are actively making better. If it turns out you need to own the interface later, the API is there and nothing you did was wasted. Or see the data first. Open the [playground](/playground) and run a real query against live production data. No key, no signup. It is the same data behind both paths. We will show you a live example on a site like yours before you commit to anything.