Vol. 01 · 2026Brand
guidelines.
Revenue infrastructure for the modern web — and the single source of truth for how its brand looks, sounds, and shows up.
BeginSet here.
Held everywhere.
Ezoic is revenue infrastructure for the modern web — the operating layer for independent web businesses. This guide is how the brand shows up everywhere it shows up.
Fixed colors. Available assets only. Direct, confident, technical. Apply with restraint and the system carries itself.
Logo.

The horizontal lockup — badge left, wordmark right — is the default in every context unless a specific variant is required.

The default surface. Off-white ink, mint badge — maximum legibility on the brand's primary background.

Print, documentation, and dual-mode exports. The badge stays green; the wordmark inverts.

Keep clear space of at least the badge height x on every side. Nothing intrudes.

Ezoic's first-party identity product carries a distinct sub-brand lockup. Use the full ezID wordmark in body copy.
Tips for proper display.
- +Use the approved palette
- +Honor original proportions
- +Keep it flat - no effects
- +Set in the original typeface
Variants.
Four approved expressions of the mark. Use the smallest piece that works for the surface.











Color.
Seven values, fixed. Near-black and Off-white carry the system. Mint is the single accent. Lime and Frog are reserved — they pair with Mint, they don't replace it.
Tap a row to copy the hex.
Type.
Inter is the preferred family for everything that reads — headings, body, UI. Red Hat Mono is limited to code, hex values, file paths, and exact technical values.
Inter
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
1234567890 !@#$%^&*()
- Headings
- Black
- Base
- Medium
- Display tracking
- −5%
- Body tracking
- −2%
Red Hat Mono
ABCDEFGHIJKLM
abcdefghijklm
1234567890 !@#$
- Required mono
- 400
- Use for
- Code · hex · paths
Voice.
Three constants. Apply them and the rest follows.
Direct.
Say what you mean. No marketing fog. No hedging that hides a weak claim.
Confident.
State verified things plainly. Confidence is about truth, not volume.
Technical.
Frame Ezoic as revenue infrastructure and an operating layer, not as a generic vendor, ad network, or plugin.
In practice.
- Build copy around setup, operating change, proof slot, quote slot, and next action.
- Use revenue infrastructure, operating layer, or infrastructure layer instead of ad network.
- Explain EPMV on first use for non-publisher audiences.
- State sourced facts plainly. If a number is unavailable, leave the metric slot open.
- Use independent web businesses when the audience is broader than publishers.
- Keep Content Integrity / Source Notes as support metadata, not as the creative lead.
Build
Components, data visualization, and the signature surface — visual specimens for applying the system. Chart values are examples, not proof points.
- Segment A46%
- Segment B28%
- Segment C16%
- Segment D10%
Grain over Mint.
Always textured. Reserved for singular brand moments — hero shapes, section anchors, ad creative.
Access.
Machine-readable setup for agents, APIs, LLM ingestion, brand logos, design-element images, photo backdrops, and fonts when available. The API, MCP tools, and LLM files include canonical style data, Content Integrity / Source Notes, and live asset truth.
Connect LLMs & Agents
Connect an MCP-capable client to the read-only server. The tools expose the canonical guide plus first-class asset records for files that actually exist in approved public roots.
Endpoint: https://iheartezoic.com/api/mcp
Asset tools: list_brand_assets, get_brand_asset
Asset roots: root=brand for available brand files, root=design-elements for reusable imagery, root=photo-backs for approved backdrops, root=fonts for public font files
{
"mcpServers": {
"ezoic-brand": {
"url": "https://iheartezoic.com/api/mcp"
}
}
}Download available brand assets.
ZIPs are generated from the same files exposed through the API and MCP. Empty roots return no downloadable assets: public/brand for logos and brand images, and public/images/design-elements for reusable visual elements if present, public/photo-backs for photo backdrops if present, and public/fonts for font files if present.

