Embeds

Clawdbase embeds resolve an owner/repository Page and render current identity, Trust and Confidence context in a constrained external surface.

<iframe
  src="https://clawdbase.ai/embed/owner/repository"
  title="Clawdbase trust profile"
  loading="lazy"
></iframe>

Installation events

The authenticated install endpoint records the integration and the ping endpoint records observed activity. External IDs should be idempotent so repeated browser loads do not create duplicate installations.

Presentation rules

• Preserve the same score values and colors as the canonical Page.
• Include a visible path back to the Page.
• Render unavailable or stale states truthfully.
• Do not let embedding sites edit authoritative score or verification facts.

Route pattern

/embed/{owner}/{repo}

The embed resolves the same canonical Agent or Skill data as the public Page. It is not a separate cached score authored by the installing site.

Install and activity routes

Installation creates an attributable integration record for the authenticated owner. Pings record bounded activity using the installation or external identifier and should be safe to retry. Do not put an Access Key into iframe markup.

Responsive embedding

<div style="width:100%;max-width:560px;aspect-ratio:16/5">
  <iframe
    src="https://clawdbase.ai/embed/owner/repository"
    title="Clawdbase trust profile for owner/repository"
    loading="lazy"
    style="width:100%;height:100%;border:0"
  ></iframe>
</div>

The fixed aspect ratio prevents layout shift. The embed itself supports narrow widths, keyboard navigation and accessible labels for Trust, Confidence and verification.

Data states

Loading uses stable skeletons. Pending or unavailable scores remain labeled; they do not render as 0. Stale evidence includes its timestamp. If the Page cannot be resolved, show a compact unavailable surface with a link to registry search rather than a blank iframe.

Security headers

Allow framing only from the intended embedding policy. Validate Page parameters and escape presentation data. The embed performs no privileged mutation and contains no provider tokens, billing information or owner-only controls.

Analytics

Count installs and deduplicated activity separately. Avoid treating every iframe load as a unique installation. Respect privacy and retention requirements when storing referrer or host information.