Skip to main content
Display your agent’s Mnemom Trust Rating anywhere. Dynamic SVG badges that update automatically, suitable for GitHub READMEs, websites, documentation, A2A Agent Cards, and package registries.
Badges are served as SVGs from a public endpoint. No authentication required.

Badge endpoint

Response: image/svg+xml with Cache-Control: public, max-age=3600, s-maxage=3600 (1-hour cache).

Badge variants

Every variant except score_tier uses the label “Trust Score”; score_tier alone uses “Mnemom Trust”. The tier name shown by score_tier comes from the canonical grade/tier table (e.g. BBB → Developing) — see Score range and grades.

grade (default)

Displays the letter grade only.

score

Displays the numeric score only.

score_grade

Displays the grade followed by the numeric score.

score_tier

Displays the numeric score with the human-readable tier label, under the “Mnemom Trust” label instead of “Trust Score”.
Best for: marketing pages, product listings, anywhere non-technical audiences will see it.

score_trend

Displays the grade and score with a directional trend arrow showing 30-day movement.
Best for: dashboards, monitoring pages, anywhere trajectory matters.
Trend arrows:
  • ↑ (up arrow): Score improved over the past 30 days
  • ↓ (down arrow): Score declined over the past 30 days
  • → (right arrow): Score unchanged

compact

Displays only the letter grade, no label — not the numeric score.
Best for: tight layouts, inline badges, status bars.

Pre-eligible agents

Agents that have not yet reached the 50-checkpoint minimum display a progress badge instead of a score, regardless of the requested variant:
This badge automatically transitions to the requested variant once the agent becomes eligible.

Private agents

Agents whose reputation visibility is set to private display a generic badge rather than leaking a score:

Not rated agents

Agents with no reputation record at all (never registered, or not yet computed) display a neutral “Not Rated” badge instead of a broken image:
This ensures badge embeds degrade gracefully.
The “Not Rated”, “Building”, and “Private” badges are all returned with the same Cache-Control header as scored badges. Once an agent is registered, becomes eligible, or is made public, the badge automatically updates.

Embed code

GitHub README (Markdown)

The most common use case. Add a clickable badge that links to the agent’s reputation page.
With tier label:

HTML websites

Standard HTML embed with link to the full reputation page.

React / JSX

A2A Agent Cards

Add a trust block to your A2A Agent Card for programmatic trust discovery:
Other agents can programmatically read the trust block to make delegation decisions. See Reputation in A2A Agent Cards for the full integration guide.
The score and grade in the A2A trust block are static snapshots that may become stale. Consumers SHOULD verify by fetching the verified_url for the latest score. The badge_url always returns the current score.

npm / PyPI package READMEs

For agents distributed as packages, add the badge to your package README: npm (package.json README):
PyPI (setup.cfg / pyproject.toml README):

Documentation sites

For Mintlify, Docusaurus, GitBook, or other documentation platforms:

Slack / Teams bot profiles

For conversational agents deployed in Slack or Microsoft Teams:
  1. Use the compact variant for profile images or status indicators
  2. Include the full reputation URL in the bot’s profile description
  3. Reference the score in bot introduction messages:

Caching behavior

Badges are cached at multiple levels: Implication: After a score change, badges may take up to 60 minutes to reflect the new value. This is intentional — frequent badge updates would increase CDN costs without meaningful benefit (scores change incrementally). For real-time score data, use the API endpoint directly:

Dark and light mode

The style query parameter (light or dark) changes only the label background — medium gray for light (the default), darker gray for dark. The value side is always colored by grade, regardless of style:
If the default badge styling does not work on your background, you can use the API response to render a custom badge. Fetch GET /v1/reputation/{agent_id} and use the grade, score, and tier fields to render your own component.

Team badges

Teams have their own badge endpoint that works identically to agent badges:
Available variants: score, grade, score_grade, score_trend, score_tier, compact Pre-eligible teams (fewer than 10 assessments) show a progress badge instead of a score:
Teams need only 10 team risk assessments for eligibility (vs. 50 integrity checkpoints for individual agents). Markdown:
HTML:
React:
Team badges use the same caching behavior as agent badges (1-hour CDN/browser cache, 5-minute internal regeneration cache).

GitHub Action: CI/CD reputation gates

mnemom/reputation-check is a GitHub Action that gates a workflow step on an agent’s minimum reputation score. See the action’s repository for current inputs, outputs, and a usage example — it is a separate open-source project from this API, so its exact interface is versioned independently.
Combine the reputation check with deployment protection rules to prevent deploying agents that have dropped below your organization’s trust threshold.

One-click copy from dashboard

The easiest way to get embed code is from your agent’s reputation page:
  1. Navigate to your agent’s dashboard
  2. Click the reputation score card
  3. Click “Embed Badge”
  4. Select a variant and format
  5. Click copy — the embed code is on your clipboard
The embed modal supports all badge variants and four formats (Markdown, HTML, React, A2A).

See also