Build on SalexHub
The REST API and the MCP server on one registry of tools, webhooks, embeds, forms, tracking and a messenger bridge: what a developer can connect today.
On this page
The Agent, workflows and API keys go through one registry of 523 tools. A call from the Agent, a workflow or an API key meets your approval rules before it runs. A call from a person, the Agent or an API key is also checked against that caller's role, and the Agent and workflows work within a budget of steps and AI credits. The app's own screens save through the registry too, except some settings, such as the organization's profile, AI settings and your own account. Since 7 October 2026 the same registry answers outside the product, over HTTP and over MCP.
Open today#
| What | What it does |
|---|---|
| REST API | One operation for each tool in the registry, at https://app.salexhub.com/api/v1, with a key from Settings as the bearer token. The OpenAPI document that describes every operation is served at the same address. |
| MCP server | The same tools for agents that speak MCP, at the same address and under the same permissions, budgets and approval rules. |
| Webhooks | Signed events to your HTTPS endpoint when a record is created or updated, and when a document moves, such as an accepted quote or an issued invoice. Retries follow a schedule, and every delivery is listed. Owners and Admins add endpoints in Settings. |
| Embeds | Live data from records you choose to publish, on any website: a script tag and a placeholder, or JSON and HTML from one address. Read-only and keyless, only the fields you name, never personal data. |
| Form endpoint | Your site's own form posts its fields to one address, and each submission lands in your organization as a contact. Comes with the Marketing hub. |
| Tracking script | One script for cookie-free page views and your own events, and identifying a visitor who gives an email. Comes with the Marketing hub. |
| Messenger bridge | A small bridge you run posts conversations from a messenger to your organization with a channel key. Replies go back by signed push or by pull. |
| AI Gateway API | Your own code calls the models your organization can run, through one OpenAI-compatible address and a key made for it in Settings > AI > AI Gateway > Keys. Each call runs on your organization's own provider key where one serves the model, otherwise on AI credits. |
| This site, for agents | Every page of salexhub.com, these docs included, is also Markdown: add .md to its address or ask for text/markdown. The index is llms.txt. |
Built, not published#
- TypeScript SDK Coming soon A generated client for the same operations, built from the OpenAPI document the API serves. It lives in the product's repository and is not published to a package registry.
Keys are issued in Settings > Developers > API keys. A key acts at the weaker of its own role and its creator's, expires after 30 days, 90 days or 1 year, and is accepted by the REST API and the MCP server: API keys, REST and MCP has the detail.
Questions about building on SalexHub go to start@salexhub.com.