Branding

Your logo and color appear in two reader-visible places:

• OAuth consent screen at /authorize — the page where users approve
  Claude, ChatGPT, or any other agent to connect to your MCP server.
• Paywall upsell payload — the JSON the MCP get_article tool returns
  when the meter is tripped. Agents render the brand colors and logo inline
  in chat.

Auto-prefill

During onboarding we look up your brand automatically:

• Logo via logo.dev, which has wordmarks/symbols for most
  publishers.
• Primary color from your homepage's <meta name="theme-color"> tag (with
  msapplication-TileColor as a fallback).

You can edit either before saving. The live preview on the Brand step shows
exactly what readers will see.

Edit later

Today, branding changes after onboarding require a PATCH against
/api/publishers/<id>:

curl -X PATCH https://builder-one-delta.vercel.app/api/publishers/<orgId> \
  -H "content-type: application/json" \
  -d '{"logoUrl":"https://...","primaryColor":"#0066ff"}'

A dashboard UI for this is on the roadmap. Until then, ping us and we'll
update it for you.

Image guidance

• Square or wordmark both work; the consent screen sizes to 40×40.
• SVG or PNG preferred. Transparent background looks best on the
  white consent card.
• Hosted on your own domain (or an obvious CDN). Hot-linked Google
  Images results will eventually break.