Glossary
tool.invoked
tool.invoked is the event type OneLifeVibe records each time a tool runs. Subscribe to tool.invoked, tool.* or * to receive runs at your HTTPS endpoint.
Updated November 12, 2026
At OneLifeVibe
- The OneLifeVibe platform pushes the same events you can read from GET /api/platform/v1/events: tool.invoked, client.approved, client.suspended, subscription.changed and world.event. Endpoints must be https on port 443 on a public hostname.
- Event types: tool.invoked, client.approved, client.suspended, subscription.changed, world.event.
- A subscription names a topic that is not a real event type or a namespace wildcard that covers one (tool.invoked, client.approved, client.suspended, subscription.changed, world.event, or tool.*, client.*, world.*, *).
What it means
tool.invoked is an event type, not a tool name or a method call. OneLifeVibe records it each time a tool runs through the platform, so it marks a single tool execution. It sits alongside client.approved, client.suspended, subscription.changed and world.event in the platform event stream.
If you are wiring up a webhook receiver, tool.invoked is the signal that a run happened. Treat it as the notification, then handle the run in your own system.
How it works
OneLifeVibe pushes events to the HTTPS endpoints you register and also exposes the same events through GET /api/platform/v1/events. A webhook endpoint must be https, use port 443 and sit on a public hostname.
Subscriptions name a topic. The topic has to be a real event type or a namespace wildcard that covers one. For tool runs, tool.invoked is the exact topic; tool.* covers every tool event, and * covers all event types. A name that is not an event type and is not a wildcard covering one is not a valid subscription topic.
When a tool runs, the platform records tool.invoked and pushes it to matching subscriptions. Your handler receives the event and can act on it. If a delivery does not reach your endpoint, read the same events from GET /api/platform/v1/events.
How OneLifeVibe uses it
OneLifeVibe uses tool.invoked as one of the five event types in its platform event stream. The others are client.approved, client.suspended, subscription.changed and world.event. The platform pushes those events and serves them from GET /api/platform/v1/events, so a webhook and a polling read see the same event types.
Use tool.invoked when your integration needs to react to a tool run. Subscribe to tool.invoked for only tool runs, tool.* if you want tool namespace events, or * if you want everything. Register an HTTPS endpoint on port 443 with a public hostname before you subscribe.
Common mistakes
The usual failure is a subscription topic that is not an event type and is not a wildcard covering one. tool.invoked is valid; tool.* and * are valid because they cover it. A made-up topic name is not.
Endpoint mistakes are just as common: http instead of https, a port other than 443, or a hostname that is not public. Check all three before you debug your handler.
Another mistake is treating tool.invoked as a client or subscription event. It records tool runs only. For client approvals, suspensions or subscription changes, use client.approved, client.suspended or subscription.changed. For everything, use *.
Questions
What event types can I subscribe to on OneLifeVibe?
The event types are tool.invoked, client.approved, client.suspended, subscription.changed and world.event. You can also use the namespace wildcards tool.*, client.* and world.*, or * for all events.
What URL can I use for a OneLifeVibe webhook endpoint?
It must be an HTTPS URL on port 443 with a public hostname. The platform pushes events to that endpoint and also serves the same events from GET /api/platform/v1/events.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.