Metadata question: how should x402scan read service logo / brand fields?

[chox-cell]

Hi x402scan team,

BeezShield is listed on x402scan here:

https://www.x402scan.com/server/54df6029-9247-458e-a5f0-6f709c0d20fb

I noticed the page shows the service correctly, but the logo/brand image is not appearing yet.

On the BeezShield side I added:

• OpenGraph image
• Twitter image
• site.webmanifest
• JSON-LD Organization logo
• additive Bazaar brand metadata under extensions.bazaar.info

Logo URL:

https://beezshield.com/brand/beezshield-logo.svg

Production checks:

• https://beezshield.com/ returns 200
• https://beezshield.com/site.webmanifest returns 200
• POST https://api.beezshield.com/agent-actions/precheck includes:
  • extensions.bazaar.info.logo
  • extensions.bazaar.info.provider
  • extensions.bazaar.info.homepage

Question: does x402scan currently read logo/brand assets from OpenGraph, web manifest, Bazaar metadata, or a separate registry field?

Not asking for promotion — just trying to make the service metadata clean and machine-readable for directories.

Thanks.

[craigbidenbot]

Hey — here's the concrete answer from the code (apps/scan/src/services/scraper/index.ts).

What x402scan currently reads for an origin's logo / brand assets:

1. <link rel="icon"> in the homepage HTML (and rel="shortcut icon"). Prioritised: SVG > large PNG (≥96px) > apple-touch-icon > standard <link rel="icon"> > /favicon.ico fallback. Stored as ResourceOrigin.favicon.
2. OpenGraph meta tags (og:image, og:title, og:description) via open-graph-scraper. Stored as OgImage rows linked to the origin. The page's main logo card uses og:image when present.
3. Standard HTML <meta> title/description as a fallback to OG.
4. api.* subdomain fallback: if the origin is https://api.example.com, the scraper also fetches https://example.com and fills in any missing favicon/OG/metadata from there. This is the path most x402 API hosts hit, since the API subdomain itself usually doesn't serve HTML.

What x402scan does NOT currently read (would be additive work):

• site.webmanifest / Web App Manifest icons[]
• JSON-LD Organization.logo
• extensions.bazaar.info.logo / .provider / .homepage from the 402 response — bazaar metadata is consumed today only for schema extraction, not for brand fields
• No separate registry field for merchant-supplied logos

For your BeezShield listing specifically:

I peeked at the rendered page. It's currently using https://beezshield.com/og-image.png (from an earlier OG scrape) and https://beezshield.com/favicon.ico as favicon. Your homepage now sets og:image to the SVG (/brand/beezshield-logo.svg) — that's correct and well-formed, it just hasn't been re-scraped yet. Origin scraping runs:

• On every resource registration on that origin (so re-registering any of your api.beezshield.com endpoints will trigger a fresh scrape)
• During the resources sync job (/api/resources/sync)

If you re-register one endpoint, your SVG og:image should land in OgImage and surface as the brand image. The favicon won't change without a code-side fix because parseFaviconFromHtml checks <link rel="icon"> tags but the SVG candidate priority depends on the type="image/svg+xml" attribute being present and the resolver succeeding — worth double-checking your <link rel="icon" type="image/svg+xml" href="favicon.svg"> returns 200.

Hope that's useful. Adding bazaar.info.logo / web manifest / JSON-LD as additional logo sources is reasonable feature work — I'd open a separate issue tagged enhancement if you want to push for it, since those are popular signals merchants are already emitting.

— Craig