ENUA

Book a demoJoin the waitlist

Sell & talk

Deliver

Run the business

Intelligence

Platform

Every module works on the same records, in your own workspace.

Developers

Your workspace, open to your code and your AI.

A public REST API with an OpenAPI 3.1 spec, webhooks in and out, and an MCP server that gives Claude and Cursor 391 tools. Each one is limited to what the key, or the person, is allowed to do.

Join the waitlistBook a demo
Capabilities · 11

One API, three ways in.

Call it from code, trigger it with webhooks, or let an AI client use it as tools.

  • 11capabilities
  • 394operations
  • 391tools

REST API

4
  • OpenAPI 3.1
  • 394 operations
  • 600 / min
  1. Public REST API with OpenAPI 3.1.222 paths and 394 operations in 42 groups: CRM, tasks and projects, catalog, orders, price lists, invoices, quotes, documents, custom entities, files, departments and employees, comments and timelines. The spec is generated from the same manifest as the API, so it can’t drift. Every workspace serves it at /api/openapi.json, no key needed.
  2. API keys.AdminNamed keys scoped to permissions, or full access, with an optional expiry. The secret is shown once, we store only a hash, and each key gets 600 requests a minute. Edit or revoke a key at any time.
  3. API reference in the app.AdminBrowse every endpoint with its auth and scope notes and a curl example, right next to your keys.
  4. Website lead capture.Post leads from your website’s forms to POST /api/leads with an API key, UTM tags and click ids included. They arrive in Leads with their source and path.

Webhooks

2
  • In
  • Out
  1. Inbound webhooks.Publish a workflow and it gets its own unguessable /api/hooks/… URL. Your systems call it (GET, POST or PUT, with an optional key) to start the workflow.
  2. Outbound webhooks.An automation rule or a stage rule on a custom record type posts to any URL you choose when something happens: a deal changes stage, a task is completed.

MCP

3
  • 391 tools
  • OAuth 2.1
  1. MCP server for Claude Desktop, Claude Code and Cursor.AdminPaste one URL and an API key. The public API becomes 391 MCP tools, filtered by the key’s scopes, with reads marked read-only.
  2. Claude on the web, without a key.AdminClaude connects by URL. The person signs in and approves scopes on a consent screen, and Claude never gets more than that person’s own rights.
  3. MCP client.Connect external MCP servers so your APROS agents can use their tools. See AI Studio

Machines and code

2
  • Claude Code
  • GitLab

The Claude Code connector and the Git module depend on your plan.

  1. Claude Code connector.AdminConnect a laptop or server that runs Claude Code. It dials out to APROS, so you open no ports. Narrow its rights to chosen scopes (never delete), see whether it’s online, paused or revoked, and let it answer in the AI Brain and take tasks. Irreversible actions wait for a person to confirm.
  2. Git module for GitLab.AdminLink projects to repositories in your company’s GitLab, or create them from a skeleton with a protected main branch. Pushes, merge requests and pipelines land on the project timeline and the task.
REST API

Your website’s form, straight into Leads.

Northwind’s site has a contact form. On submit, it posts the name, email, message and the visitor’s UTM tags to POST /api/leads with an API key that can only create leads. The lead appears in APROS with its source, campaign, landing page and the pages the visitor saw, and the team picks it up from the board.

MCP server

Ask Claude about your pipeline. Give it read access, nothing more.

An admin creates an API key that can read leads and deals and do nothing else, then pastes the MCP URL and the key into Claude Desktop. Claude sees only the tools that key allows, and every write tool stays out of reach. A colleague on Claude on the web connects without a key: they approve the scopes on a consent screen, and Claude can’t exceed their own rights.

Claude Code connector

Hand a task to a machine, and keep a person on the last step.

A developer connects their build server running Claude Code. A project manager assigns it the task “Add the delivery-date field to the order export”. The machine picks it up, comments in the task thread as it works, and with the Git module it gets a repository token that is revoked when the task ends. Anything irreversible waits for a person to confirm. Claude Code runs on your machine, under your own Anthropic account.

Webhooks

Start a workflow from any system, and tell any system what happened.

Northwind’s warehouse software calls a workflow’s webhook URL when a shipment leaves. The workflow adds a comment to the delivery task and notifies the account manager. In the other direction, an automation rule posts the deal to the accounting system’s URL when it’s marked Won.

AI clients

Bring your own AI to your own data.

  1. Claude and Cursor as clients.Connect Claude Desktop, Claude Code or Cursor with a key, or Claude on the web through a consent screen, and they work with your APROS data as tools.
  2. A machine that answers in the Brain.In the AI Brain, pick a connected Claude Code machine under “Who answers”, and choose its model.
  3. More tools for your agents.Connect external MCP servers, and APROS agents use their tools alongside their own.

See AI Studio

Connected

Connected to the rest of APROS.

  • Projects & tasks

    A task’s assignee can be a person, an AI agent or a Claude Code machine, and a project can be bound to a GitLab repository.

    See Projects & tasks

  • Automation

    Outbound webhooks are an automation action, and inbound webhooks start workflows built on the visual canvas.

    See Automation

  • AI Studio

    Connect MCP servers there, and give their tools to the agents that need them.

    See AI Studio

  • Sales

    Leads posted through the API arrive with their attribution and land on the board like any other lead.

    See Sales
FAQ

Developer questions.

Where is the API documented?

Every workspace serves an OpenAPI 3.1 spec at /api/openapi.json, no key needed. Admins also get a reference with curl examples next to their API keys.

How are API keys limited?

Each key is scoped to the permissions you choose, can expire, and is limited to 600 requests a minute. The secret is shown once and stored only as a hash. You can edit or revoke a key at any time.

Which AI clients can connect over MCP?

Claude Desktop, Claude Code and Cursor connect with a URL and an API key. Claude on the web connects through a consent screen, with no key.

Do you have event webhooks?

Yes, through automation. A rule or a workflow step posts to your URL when something happens, like a stage change or a completed task. In the other direction, a published workflow gets its own URL that your systems can call. There’s no separate subscription registry.

Which Git hosts does the Git module support?

GitLab, including your company’s own GitLab.

Build on APROS from day one. Join the waitlist to be first in, or book a demo and bring your integration questions.

Join the waitlistBook a demo