Approval Routing is live. Here’s where to start. Different workflows need different updates. You might need to know when a request is waiting for approval, when a decision has been made or both. $VETO lets you configure an HTTPS webhook endpoint and select the events it receives including approval requests and approval resolutions. You can also limit delivery to your own events rather than the whole workspace. For developers, this provides a starting point for connecting Veto to an external notification workflow. A webhook endpoint is the receiving service; it is not automatically a ready-made Slack, email or push integration. Start with the events you need, configure your endpoint and test delivery before relying on it. Explore the Alerts section: app.vetoprotocol.live

Meet Approval Routing - Next feature we’re preparing for $VETO. Its purpose is straightforward: when an agent reaches an action that requires your approval, help that request reach you beyond the dashboard. The intended workflow is: - An agent submits a request through Veto. - Veto determines that human approval is required. - A supported notification channel alerts you. - You review the request through Veto and approve or deny it. This is a delivery improvement around the approval process. It doesn’t give the agent new permissions or change a blocked action into an allowed one. We want agents to be useful without making users constantly watch over a dashboard. Approval Routing is one step toward making that experience more practical. Stay tuned!

Meet Approval Routing - Next feature we’re preparing for $VETO. Its purpose is straightforward: when an agent reaches an action that requires your approval, help that request reach you beyond the dashboard. The intended workflow is: - An agent submits a request through Veto. - Veto determines that human approval is required. - A supported notification channel alerts you. - You review the request through Veto and approve or deny it. This is a delivery improvement around the approval process. It doesn’t give the agent new permissions or change a blocked action into an allowed one. We want agents to be useful without making users constantly watch over a dashboard. Approval Routing is one step toward making that experience more practical. Stay tuned!

Agent Fingerprints - See What’s Connecting as Your Agent You know what your agent is allowed to access. But which program is using that access? This demo shows how Agent Fingerprints brings that activity into view: the client name, reported versions, first and last seen, request count and trust status all grouped by agent. In the walkthrough, Claude Code updates between two requests. Veto records the version change under the same client without treating a routine update as unfamiliar software. Choose how each agent handles a new client: • Record only: Log the connection without changing authorization decisions. This is the default. • Ask me: Require your approval with a passkey before new software can act. • Refuse: Reject new software before policy evaluation or contact with the connected service. The first client an agent uses is trusted automatically. Newly encountered clients after that trigger an alert through your configured webhook including in record-only mode. Agent Fingerprints adds visibility and another access check. It does not replace your policies. Delegate intelligence. Retain authority.

Robinhood Chain is built for tokenized real-world assets and the apps people actually want to use with them. Usage follows utility: great assets, great builders, and plugging it into the Robinhood products millions of customers already use. More to come.