Skip to main content
PUT
/
agents
/
{agent_id}
/
alignment-card
DEPRECATED — use PUT /v1/alignment/agent/{agent_id}.
curl --request PUT \
  --url https://api.mnemom.ai/v1/agents/{agent_id}/alignment-card
{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}
Publishes a new alignment card for an agent.
Deprecated URL. This per-agent path 308-redirects to the canonical PUT /v1/alignment/agent/{agent_id} (sunset 2027-01-15, then 410 Gone). Publish to the canonical URL directly — see the Card Management guide and Unified cards overview.
Authorization is by organization membership: any member (owner/admin/member) of the org that governs the agent may publish; the org is derived server-side; non-members get 403 agent_org_forbidden. (Enforced on the canonical endpoint the redirect lands on.)

Required headers

Idempotency-Key: <opaque 24h-unique string>
The handler runs a two-phase reserve / finalize / release on the key. Replays of the same key with the same request body return the cached response. Replays with a different body return 422 Idempotency-Key conflict.

Body shapes

Content-TypeBody
text/yamlRaw YAML card document
application/yamlRaw YAML card document
application/jsonRaw card object, or { "card_yaml": "<yaml string>" }, or { "card_json": {...} }
The card body must include values, autonomy, and commitments blocks at minimum. See the alignment card schema for full requirements.

Side effects

  • Writes a governance_audit_log row before responding (synchronous; failure aborts).
  • Emits the alignment_card.updated webhook event (see Webhooks guide).
  • Triggers recompose of any teams the agent belongs to.

Body size limit

128 KB. Two-layer check (Content-Length, then body length).

See also

Path Parameters

agent_id
string
required

Agent identifier (e.g. smolt-abc123)

Response

Permanent Redirect (RFC 7538). This URL is deprecated; follow Location to the canonical /v1/<resource>/<scope>/<scope_id> shape. Method and body are preserved across the redirect — modern clients re-issue the same PUT / POST / DELETE against the target unchanged.