Skip to content

For developers

API → MCP

Use the same integrations, permissions and approvals from AI clients and your own applications.

Remote MCP

https://vezista.io/mcp

Streamable HTTP, OAuth with PKCE, dynamic client registration and permission-scoped tool discovery.

Every permission profile has its own MCP address, under AI assistants in the workspace: an AI app connected with it works only with that company and its permissions. At the shared address above you choose the workspace and permission profile on the consent screen.

REST API

https://vezista.io/api/v1/tools

Create a scoped token in your workspace. Tool schemas and permitted actions are returned by this endpoint.

The same token works in an AI app that takes a token instead of a sign-in, at the MCP address of its permission profile.

curl https://vezista.io/api/v1/tools \
  -H 'Authorization: Bearer YOUR_TOKEN'

One execution policy

A write requires an idempotency key. An action awaiting approval returns an approval URL; it runs only after an authorized person approves the exact request.

Poll the invocation endpoint or use get_invocation over MCP for the result. A queued or pending action is not a successful action.

Create a workspace →