Skip to main content

Endpoint Update

When you have significant new information about an existing endpoint, delegate the update to the update-endpoint subagent. The subagent verifies your claims, extends the documentation, and ensures quality is maintained.

When to Use This​

  • Discovered new parameters or headers during deeper testing
  • Found rate limit headers (X-RateLimit-*) not in the original docs
  • Auth requirements changed or were incorrectly documented
  • Found security observations (IDOR, data exposure, etc.)
  • Got a different response than documented (API behavior changed)
  • Found new response status codes or error formats

Do NOT use for minor observations — use save_memory(references=["endpoint://ID"]) for small notes. Use this when the endpoint's core documentation needs updating.

Quality Rules​

  1. Description only grows — the new description must be at least as long as the current one
  2. Reason required — you must explain what new information you discovered
  3. Verify before updating — the subagent curls the endpoint to confirm your claims
  4. Merge, don't replace — new headers/examples/schema are ADDED to existing

How to Delegate​

Agent("update-endpoint", "Endpoint 42 (POST /api/v2/users/search) needs update.
Found X-RateLimit-Limit: 100 and X-RateLimit-Remaining headers in responses.
Also discovered that the 'role' filter parameter only works for admin accounts —
regular users get 403 when filtering by role=admin.")
Agent("update-endpoint", "Endpoint 15 (GET /api/health) needs update.
Previously documented as no auth required, but now returns 401 without
a valid session cookie. Auth mechanism changed.")

Rules​

  • To update endpoint documentation, always delegate to the update-endpoint subagent
  • For small observations, use save_memory(references=["endpoint://ID"]) instead
  • Wait for the subagent to complete before continuing