Skip to main content

Mnemom Trust Rating API

The Trust Rating API provides programmatic access to Mnemom Trust Ratings, historical trends, embeddable badges, directory search, bulk lookups, and aggregate benchmarks. All reputation data is computed from independently verified AIP integrity checkpoints. Base URL: https://api.mnemom.ai/v1/reputation

Authentication

API key authentication: Pass in the Authorization header:
API keys can be created in your dashboard under Settings or via POST /v1/api-keys.

Rate limits

Reputation endpoints are rate-limited to prevent systematic enumeration. Limits are applied per-IP for unauthenticated requests and per-API-key (JWT sub) for authenticated requests. Badge and OG-image endpoints have generous limits because they are typically embedded in websites and served through CDN caching. Authenticate requests (via Authorization: Bearer <token>) to access higher limits.

429 response format

Rate limit windows are 1 minute. Enterprise customers requiring higher limits should contact support.

Endpoints

GET /v1/reputation/

Retrieve the full reputation score for an agent, including all five component scores, trend data, and confidence level. Parameters: Response: 200 OK
Response fields: a2a_trust_extension object: Component object: Error responses:

GET /v1/reputation//history

Retrieve weekly reputation snapshots for trend analysis. Parameters: Response: 200 OK
Snapshot object:

GET /v1/reputation//badge.svg

Dynamic SVG badge showing the agent’s current reputation score. Parameters: Response: 200 OK with Content-Type: image/svg+xml
Badge variants: For agents below the 50-checkpoint minimum:
See Embeddable Badges for embed code in Markdown, HTML, React, and A2A formats.

GET /v1/reputation//verify

Cryptographic verification of a reputation score. Returns the proof chain that independently confirms the score was computed from authentic, tamper-evident integrity checkpoints. Parameters: Response: 200 OK
Response fields: verification object: Error responses:
Use the verification endpoint to independently confirm that a reputation score is backed by real integrity data. The certificate_hash can be cross-referenced with the certificate endpoint and the merkle_root can be verified via the Merkle root endpoint.

POST /v1/reputation/batch

Retrieve reputation scores for multiple agents in a single request. Requires API key authentication. Request body:
Response: 200 OK
Error responses:

GET /v1/reputation/search

Search the reputation directory for agents by name, grade, or confidence level. Requires API key authentication. Query parameters: Response: 200 OK
Directory agent object:

GET /v1/reputation/compare

Side-by-side comparison of 2 to 10 agents. Requires API key authentication. Query parameters: Example:
Response: 200 OK
Error responses:

GET /v1/reputation/benchmarks

Aggregate statistics across all publicly scored agents. Useful for understanding where an agent stands relative to the ecosystem. Response: 200 OK
Benchmark fields:

Webhook events

Subscribe to reputation-related webhook events via Webhook Notifications:
Fires when an agent’s reputation score changes by more than 10 points (positive or negative) during hourly recomputation.
Fires when an agent’s letter grade changes (e.g., from BBB to A). Always accompanied by a reputation.score_changed event.

Error codes

All error responses follow the standard envelope:

SDK usage

TypeScript

Python


See also