agent-data-api-endpoints

To synchronize API endpoint changes, update contract schemas first, then propagate those changes through manifests, server route handlers, typed SDK methods, agent call sites, tests, and documentation to maintain a consistent stack.

Managing endpoint additions and deletions requires coordinating updates across contract schemas and manifests first, then aligning server routes, SDK methods, agents, tests, and docs to ensure all related artifacts stay in sync.

API contract schemas and SDK methods fall out of sync when endpoint modifications are not propagated end-to-end across manifests, server handlers, agent consumers, tests, and documentation in a coordinated, contract-driven workflow.

No, you should update contract schemas first, then align manifests and server route handlers with the updated contracts before propagating changes through typed SDK methods, agent call sites, tests, and docs.

Yes, this coordination process explicitly applies to endpoint addition, modification, and deletion scenarios, ensuring changes propagate through SDK methods and agent call sites to keep agent consumers fully synchronized.

Manually updating API endpoints without contract-driven synchronization risks breaking agent consumers, failing tests, and desynchronizing manifests, server handlers, SDK methods, and documentation across the stack.