Skip to main content
Each call carries an API path, an HTTP method, and — where the endpoint needs them — query parameters, a request body, and headers from the vendor’s allowlist. Neo adds the base URL and the authentication, so the agent never handles the credentials, and a header outside the allowlist is rejected. A vendor the agent’s permissions do not cover is rejected before any HTTP call, and so is a vendor whose permissions are on but which is not connected on the Integrations page.
Automatically enabled when you configure permissions for any of the covered vendors in your agent workflow. No manual toggle needed — and it never appears as a separate tool to configure.
The agent’s instructions list the vendors your permissions enable, with a line on what each one covers. A vendor you enabled but have not connected is listed as not connected, so the agent tells you it needs connecting instead of calling it. The endpoint tables, request shapes, and each vendor’s quirks live in that vendor’s skill, which the agent must load before its first call to the vendor.

​
What It Does

  • Calls the vendor’s REST API directly — reads and (where permitted) writes
  • Routes each call through the vendor’s own permission groups, exactly as the former per-vendor tools did
  • Applies the vendor’s approval rules. Some operations always wait on a technician, whatever the agent’s settings, such as deleting a core record (a company, site or organization), removing an endpoint’s protection (an uninstall, a deactivation, a mode or code that stops blocking), wiping or retiring a device, turning off a service’s automatic backups, sending as the customer, and a write Neo cannot classify. Each vendor’s own docs list them, under “Safety Controls” or “Changes that always ask a technician”. Every other write follows the permission group’s Require Technician Approval setting

​
Covered Vendors

​
Permissions & Billing

Each vendor keeps its own permission groups in the agent’s settings — enabling one vendor never grants another. On a scheduled or chat agent each call prices by what it did (Tool credit costs), and usage reporting keeps the per-vendor split.