---
title: "Create a trust edge from this agent to another"
method: POST
path: "/agents/{agent_id}/trust-edges"
tags: ["Agents"]
---

# Create a trust edge from this agent to another

`POST /agents/{agent_id}/trust-edges`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/agents/{agent_id}/trust-edges`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Caller must be an owner, admin or member of the `from` agent's org (or a platform admin). `to_agent` may be in the same org, or in another org when its reputation visibility is `public` or `unlisted`; a private or tombstoned agent in another org returns the same 404 as a nonexistent agent. `weight` is clamped to [0, 1] with default 0.5. Returns 409 if an edge already exists in the same direction.

## Path parameters

- `agent_id` string, required

## Request body

- object
  - `to_agent` string, required
  - `weight` number
  - `reason` 'team_membership' | 'manual' | 'org_co_membership': Edge provenance. Constrained to a fixed set; an out-of-set value returns 400.

## Response `201`

Edge created.

- object: Directed trust-relationship edge between two agents (CLPI Phase 3). Used by the trust-topology RPC and the team reputation scorer.
  - `id` string: Prefixed `te-…` identifier.
  - `from_agent` string
  - `to_agent` string
  - `weight` number
  - `reason` string: Free-form label (e.g. `manual`, `roster_coherence`, `co_deployment`).
  - `created_at` string, date-time
  - `created` boolean

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `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)