Point this agent's Google traffic at your own endpoint

This is Google's inbound routing for one agent — it is not how you receive messages from Cadence. It tells Google to push this agent's traffic to a URL of your own instead of to the partner-level endpoint that Cadence normally receives on, which means Cadence stops seeing that agent's replies and stops driving its flows.

If what you want is your application to learn about inbound replies, you want a flow (the server answers for you), GET /v1/events (SSE), or GET /v1/conversations/{id}/answers (polling) — see the guide at https://cadencercs.com/docs.html#receiving.

We issue the verification token rather than accepting one, so it is always high-entropy. It is derived, not stored — re-issuing returns the same value; ?rotate=true invalidates the old one. Your endpoint must echo the token on Google's verification handshake, and every push is signed with it.