---
title: "Verify team reputation cryptographically"
method: GET
path: "/teams/{team_id}/reputation/verify"
tags: ["Team Reputation"]
---

# Verify team reputation cryptographically

`GET /teams/{team_id}/reputation/verify`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/teams/{team_id}/reputation/verify`
- Auth: none required

Public endpoint. Returns the team's reputation score with a cryptographic proof hash for independent verification.

## Path parameters

- `team_id` string, required

## Response `200`

Reputation with verification proof

- object
  - `team_id` string
  - `score` number
  - `grade` string
  - `computed_at` string, date-time
  - `verification` object, nullable
    - `proof_hash` string
    - `computed_at` string, date-time
    - `total_assessments` integer

## Other responses

- `400`: Bad request
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)