New: MCP server monitoring is live. Start free trial
VercelSchemaBehavioral

Fields removed in POST /v1/projects/{idOrName}/avatar response 200: [delegatedProtection]

Affected surface
POST /v1/projects/{idOrName}/avatar

What changed

Fields removed in POST /v1/projects/{idOrName}/avatar response 200: [delegatedProtection] Affected surface: POST /v1/projects/{idOrName}/avatar. Root cause: endpoint `POST /v1/projects/{idOrName}/avatar`. Detected at Fri, 29 May 2026 18:29:05 UTC UTC.

Diff

{
  "path": "POST /v1/projects/{idOrName}/avatar",
  "removed_fields": [
    "delegatedProtection"
  ],
  "schema_path": "POST /v1/projects/{idOrName}/avatar response 200"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.