Attribution & branding

This document defines how Integrators MUST credit Merkl when displaying Merkl-sourced data in their products. It covers all data retrieved through the Merkl API (api.merkl.xyz), including opportunities, campaigns, APRs, TVL, reward distributions, and any Derived Values.Who this applies to: Any team, company, or individual integrating Merkl data into a website, application, dashboard, widget, or any other page or UI view.When to read this: Before launching any product or feature that displays Merkl-sourced data or merkl contracts. Compliance is required at launch and on an ongoing basis.Any call to action that triggers a claim of Merkl-distributed rewards MUST display Merkl attribution on the action element and link to the corresponding page on app.merkl.xyz.

By using the Merkl API, Integrators agree to comply with these guidelines. Non-compliance will result in API access being throttled or revoked.

1. Standard attribution

Integrators MUST attribute Merkl on every page or UI view where Merkl-sourced data appears.For each page or UI view, Integrators MUST include:

A link to https://app.merkl.xyz, or to the specific opportunity page when displaying a single opportunity, or to the protocol page.

And at least one of the following two elements, placed within the same visual container as the data (e.g. the same card, panel, table, or section):

The official Merkl logo, taken from the Merkl Brand Kit (see §4).
The "Powered by Merkl" logo or a written text version to fit visual constraints.

Attribution MUST NOT be placed in a separate page section, global footer, settings screen, or any location that requires scrolling or navigating away from the data it references.

1.1 Per-view attribution

Integrators MUST display attribution on every page or UI view where Merkl-sourced data is rendered.Placing attribution only on an "about", "partners", or "credits" page does not satisfy this requirement.Every page, tab, table row or view that displays Merkl-source data MUST include Merkl attribution and deeplink to that specific opportunity on app.merkl.xyz.When a page or UI view displays a single opportunity or campaign, the attribution MUST deeplink to that specific opportunity on app.merkl.xyz.

Inline badge in card

USDC Pool

Aave · Base

12.4% APR

Updated 2m ago

View on Merkl ↗

Buried in global footer

USDC Pool

Aave · Base

12.4% APR

Updated 2m ago

Data sources at /credits

2. Claim attribution

2.1 Claim CTA requirements

The claim call to action MUST:

Display the Merkl logo on or directly adjacent to the button
Use one of the following approved labels:
- "Claim via Merkl",
- "Claim on Merkl", or
- "Claim rewards on Merkl".
Integrators MUST NOT rephrase or remove "Merkl" from the label.
Link to the corresponding claim flow on app.merkl.xyz

Claim via

Merkl

2.2 Button specs

Property	Dark mode	Light mode
Background	`#7653FF`	`#8D77FF`
Text color	`#FFFFFF` Aeonik SemiBold, 16px	`#FFFFFF` Aeonik SemiBold, 16px
Border radius	Pill (full rounding)	Pill (full rounding)
Padding	8px 12px	8px 12px
Gap	4px between text and wordmark	4px between text and wordmark
Min height	44px	44px
Width	Full container width	Full container width
Logo	Full Merkl wordmark, white, inline after "Claim via"	Full Merkl wordmark, white, inline after "Claim via"

Integrators MUST NOT restyle the claim button to match their own brand colors. The claim CTA MUST be visually identifiable as a Merkl action.

2.2.1 Embed reference

Integrators MAY use the following CSS reference to implement the claim button. A hosted embed component will be provided in a future version of these guidelines.

html · css

<a href="https://app.merkl.xyz/opportunities/{id}"
   class="merkl-claim-btn"
   target="_blank" rel="noopener noreferrer">
  Claim via
  <svg class="merkl-wordmark" aria-label="Merkl">...</svg>
</a>

.merkl-claim-btn {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 4px;
  width: 100%;
  padding: 8px 12px;
  background: #8D77FF;
  color: #FFFFFF;
  font-family: 'Aeonik', sans-serif;
  font-size: 16px;
  font-weight: 600;
  text-decoration: none;
  border: none;
  border-radius: 30px;
  cursor: pointer;
}

.merkl-claim-btn .merkl-wordmark {
  height: 18px;
  width: auto;
  fill: #FFFFFF;
}

Integrators MUST NOT modify the background color, border radius, wordmark, or label text of this component.

2.3 Prominence

The claim CTA MUST be displayed with equal or greater prominence than any other action on the same page or UI view.It MUST NOT be visually smaller, lower contrast, or secondary to the integrator's own buttons.

2.4 Placement

The claim CTA MUST:

Be visible without scrolling on the page or UI view where rewards are displayed
Not be obscured by pop-ups, tooltips, banners, or other overlays
Appear within the same visual container as the reward data it references

2.5 Confirmation

After a claim is initiated, any confirmation or success state MUST still display Merkl attribution (logo or "Powered by Merkl").The integrator MUST NOT present the completed claim as their own service.

2.6 Prohibited claim patterns

Integrators MUST NOT:

Use generic labels like "Claim rewards" or "Collect" without mentioning Merkl
Present the claim action as a feature of the integrator's own platform
Redirect the claim through an intermediary flow that strips Merkl branding
Self-host or recreate the Merkl logo for claim buttons (use Brand Kit assets only)

3. Logo & wordmark usage

The Merkl Brand Kit is available at https://merkl.xyz/brand. Inside the dev portal, see Brand assets.

4. Prohibited practices

Integrators MUST NOT:

Present Merkl-sourced data as their own proprietary data.
Use phrasing such as "our data shows" or "according to our analysis" when the underlying data comes from Merkl.
Attribute Merkl-sourced data to a different source, or combine it with other sources in a way that obscures the origin.
Strip, obscure, or minimize attribution to the point of being effectively invisible.
Imply affiliation, partnership, or endorsement by Merkl without prior written consent.
Use "Merkl" in a product name, domain, or app-store listing in a way that suggests endorsement, without prior written consent.

5. Exceptions & contact

Integrators MUST submit any custom attribution layout to Merkl for approval before publishing.For questions, exception requests, or brand asset access, contact your Merkl account manager.

6. Contact

Brand assets & Brand Kit access
Attribution questions & exception requests
General contact

Further context on Merkl and its data model: docs.merkl.xyz .