Install Jentic One Beta

Connect the malma Workspace API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the malma Workspace API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmalma.ai%2Fmalma" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmalma.ai%2Fmalma" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with malma Workspace API.

List every agent configured in a malma workspace with their IDs and metadata

Create a new lead in a workspace and route it to a chosen agent

Pass enrichment fields on the lead so the malma agent can personalise outreach

Drive the lead-creation step from a Make.com or Zapier scenario

Look up workspace agent IDs to validate downstream automation configuration

GET STARTED

Start building with malma Workspace API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use malma Workspace API for, with concrete tasks.

★ Webform-to-Malma Lead Handoff

Marketing teams that capture leads on a website want them to reach a malma.ai voice or chat agent immediately. The malma create-lead endpoint accepts the lead's contact and enrichment fields plus the target agent ID, so a webform handler can POST the lead the moment the form is submitted. The agent then picks up outreach without any human in the loop.

POST /workspace/create-lead with the form fields and the target SDR agent ID, then verify the lead lands in the workspace.

Make.com or Zapier Workflow

The malma API is built for no-code automation tools. A Make.com or Zapier scenario can list the workspace agents to populate a dropdown for non-technical users, then create the lead against the selected agent on a downstream trigger. This is the canonical integration path for the malma platform.

GET /workspace/agents to populate the dropdown, then POST /workspace/create-lead with the user-selected agent ID and the trigger payload.

Chat-Qualified Prospect Routing

Live chat tools that qualify visitors can hand off the qualified prospect to a malma voice or chat agent for follow-up. The create-lead endpoint accepts the qualification metadata as part of the lead body so the malma agent picks up the conversation with full context.

On chat qualification, POST /workspace/create-lead with the conversation summary in the lead's enrichment fields and the SDR agent ID.

AI Agent Lead Generation Loop

Outbound and inbound agents can generate leads in malma as part of a wider workflow. Through Jentic the agent searches by intent, loads the schema, and executes the create-lead call while the workspace bearer token stays in the vault. The narrow API surface makes it ideal for agent-as-tool patterns.

Use Jentic to search 'create malma lead', execute POST /workspace/create-lead with the resolved contact and target agent, and return the new lead ID.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for malma workspace api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/workspace/agents

Get workspace agents

POST

/workspace/create-lead

Create lead

GET

/workspace/agents

Get workspace agents

POST

/workspace/create-lead

Create lead

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the malma Workspace API by hand means managing its bearer token, targeting the app.malma.ai/api host, and handling its agent-listing and lead-creation calls yourself. Through Jentic you install once, import malma from the API Directory, store the token once, and your agent calls it.

Permission scoping

malma exposes two operations, listing workspace agents and creating a lead, with the lead details carried in the request body, so limit the agent to the operations it needs, such as reading the agent list, and add lead creation only when you want it. The operation set is your choice.

Credential isolation

Your malma Workspace API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list workspace agents' or 'create a lead', and Jentic returns the matching malma operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using malma Workspace API through Jentic.

Why is there no official OpenAPI spec for malma Workspace API?

malma does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call malma Workspace API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the malma Workspace API use?

malma uses HTTP bearer authentication scoped to a workspace. Through Jentic the bearer token is stored encrypted in the vault and attached at execute time, so the agent never sees the raw token.

Can I create a lead through the API?

Yes. POST /workspace/create-lead with the contact details and the target agent ID. The agent picks up the lead inside the workspace once the call returns.

How do I find the right agent ID to route a lead to?

Call GET /workspace/agents to list every agent in the workspace, then pick the agent whose name or persona matches the routing rule for the lead.

What are the rate limits for the malma Workspace API?

Rate limits are not declared in the OpenAPI spec - they depend on the malma plan attached to the workspace. Check the malma.ai dashboard before sending high-volume lead bursts.

How do I create a lead through Jentic?

Run pip install jentic, search 'create malma lead', load the schema for POST /workspace/create-lead, and execute with the contact details and target agent ID. Jentic injects the bearer token from the encrypted vault.

Can I limit what my agent is allowed to do with the malma Workspace API?

Yes. Because you run Jentic One yourself, your own rules decide which malma operations and credentials the agent may use. The malma Workspace API exposes just two operations, listing workspace agents with GET /workspace/agents and creating a lead with POST /workspace/create-lead, so you can allow the agent to read the agent list only and add lead creation with POST /workspace/create-lead solely when you want it. The operation set the agent can call is your choice.

malma Workspace API

AI ReadinessAI-Aware (A-)73/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticCRMContact Managementbearer2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List malma.ai workspace agents and create new leads inside a workspace. Used by automation workflows that hand qualified leads off from a website, form, or chat experience to a malma agent.

Use for: I need to push a new lead to a malma workspace from a webform, List all agents in the malma workspace, Create a lead and route it to a specific malma agent ID, Find the agent ID for the SDR malma persona

Not supported: Does not handle outbound calling, agent training, or workspace administration - use for listing workspace agents and creating leads only.

Jentic publishes the only available OpenAPI specification for malma Workspace API, keeping it validated and agent-ready. The malma Workspace API is the official surface for the Make.com and Zapier integrations with malma.ai. It provides two workspace-scoped endpoints: list the agents available in a workspace and create a new lead inside it. Authentication uses a bearer token tied to the workspace.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

19%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

78%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the malma Workspace API to your agent

Capabilities

Start building with malma Workspace API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

malma Workspace API

Jentic AI Readiness Score

malma Workspace API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness