Install Jentic One Beta

Connect the Moveo.AI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moveo.AI, 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%2Fmoveo.ai%2Fmoveo" | 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%2Fmoveo.ai%2Fmoveo" | 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 Moveo.AI API.

Open a session on a desk, send it a message with input and context, and read the session transcript

Train a brain from intents, entities, and dialogs, then create, diff, and publish versions

Search a knowledge base by natural-language query and publish or draft its documents

Connect datasources to a knowledge base and track their sync status

Route live conversations with desk rules, departments, SLAs, business hours, and capacity policies

GET STARTED

Start building with Moveo.AI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Moveo.AI API for, with concrete tasks.

★ Agent that talks to a Moveo virtual assistant on a customer's behalf

An orchestrating agent can hand a customer question to a Moveo virtual assistant without a developer wiring the Authorization header, the right regional host, and session handling by hand. Through Jentic the agent searches for 'send a message to a Moveo session', loads the session message operation with its input schema, and sends the input and context. Your own Jentic One instance attaches the key at call time, and the reply comes back from the brain configured on that desk.

Call POST /v1/desks/{desk_id}/sessions to open a session, then POST /v1/desks/{desk_id}/sessions/{session_id}/message with input and context, and return the assistant's reply

Improving a brain from real conversations

Conversation designers refine a brain by adding intents and entities, generating an intent from sample expressions, and reviewing and flagging the recommendations Moveo returns for the brain. Once changes are ready, a retrain is queued, the new version can be diffed against the previous one, and the version is published.

Call POST /v1/brains/{brain_id}/intents to add an intent, POST /v1/brains/{brain_id}/train to queue a retrain, then POST /v1/brains/{brain_id}/publish

Grounding answers in a knowledge base

Support assistants answer from company documents held in Moveo knowledge bases. Datasources connected to a knowledge base sync documents in, drafts can be published to make them searchable, and a search call returns up to 20 matching documents for a natural-language query.

Call POST /v1/collections/{collection_id}/search with query 'how do I return an item' and limit 5, and summarise the top documents

Monitoring a live support desk

Support leads need a view of workload across a desk. Conversation counts by status, by agent, and by department show where queues are building, and individual conversations can be fetched or updated. Routing rules, SLAs, and business hours can be adjusted on the same desk.

Call GET /v1/desks/{desk_id}/conversations/counts and GET /v1/desks/{desk_id}/conversations/department-counts, then flag any department whose active count exceeds 20

Key Endpoints

308 endpoints — the moveo.

METHOD

PATH

DESCRIPTION

POST

/v1/desks/{desk_id}/sessions

Create a session

POST

/v1/desks/{desk_id}/sessions/{session_id}/message

Send message to a session

GET

/v1/desks/{desk_id}/sessions/{session_id}/transcript

Get session transcript

POST

/v1/collections/{collection_id}/search

Search a knowledge base

POST

/v1/brains/{brain_id}/train

Queue a brain retrain

POST

/v1/brains/{brain_id}/publish

Publish a brain version

GET

/v1/desks/{desk_id}/conversations

List conversations

POST

/v1/desks/{desk_id}/conversations/outbound

Send outbound message

POST

/v1/desks/{desk_id}/sessions

Create a session

POST

/v1/desks/{desk_id}/sessions/{session_id}/message

Send message to a session

GET

/v1/desks/{desk_id}/sessions/{session_id}/transcript

Get session transcript

POST

/v1/collections/{collection_id}/search

Search a knowledge base

POST

/v1/brains/{brain_id}/train

Queue a brain retrain

POST

/v1/brains/{brain_id}/publish

Publish a brain version

GET

/v1/desks/{desk_id}/conversations

List conversations

POST

/v1/desks/{desk_id}/conversations/outbound

Why Jentic?

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

Setup

Wiring Moveo.AI by hand means choosing a JWT or an API key of the right type, picking the Europe, United States, or Brazil host for your account, and threading desk, brain, and session ids through every call. Through Jentic you install once, import Moveo.AI from the API Directory, store the key once, and your agent calls it.

Permission scoping

Moveo puts the desk_id, brain_id, and collection_id in the URL path, as in /v1/desks/{desk_id}/sessions, so a rule can hold your agent to one desk or one brain and the operations you pick. You choose the operations it may call, so destructive ones like deleting a brain or a conversation are not included unless you add them.

Credential isolation

Your Moveo.AI key 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 'send a message to a Moveo session' or 'search the knowledge base', and Jentic returns the matching Moveo.AI operation with its input schema out of the full operation set.

FAQs

Specific to using Moveo.AI API through Jentic.

What authentication does the Moveo.AI API use?

Per its OpenAPI spec, the Moveo.AI API accepts either a JWT bearer token or an API key sent in the Authorization header. API keys come in two types: manage keys for brains, broadcasts, campaigns, collections, desks, plugins, and roles, and use keys limited to sessions, message, and classify. Through Jentic the key is stored by your own Jentic One instance and attached at call time.

Which regional host should I call for the Moveo.AI API?

The spec lists three servers: https://api.moveo.ai/api for Europe, https://api.us-central.moveo.ai/api for the United States, and https://api.sa-east.moveo.ai/api for Brazil. Use the host for the region your Moveo account lives in.

What are the rate limits for the Moveo.AI API?

The OpenAPI spec does not specify rate limits. Check the Moveo documentation at https://docs.moveo.ai for current limits.

Is there a Moveo.AI MCP server?

You don't need an MCP server to give your agent Moveo.AI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls session, knowledge base, and desk operations on demand without another server's tool definitions in its context.

Can I limit what my agent is allowed to do with the Moveo.AI API?

Yes. Write a rule that allows only the session create, session message, and transcript operations under one desk_id, so the agent can hold conversations on that desk but cannot delete brains, change routing rules, or launch campaigns. Every call it makes is logged.

How do I search a Moveo knowledge base through Jentic?

Search Jentic for 'search a Moveo knowledge base', load the POST /v1/collections/{collection_id}/search operation, and execute it with a query and an optional limit up to 20. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Moveo.AI

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsChat Messagingbearer, apiKey308 EndpointsREST

For Agents

Send messages to Moveo.AI conversational agents, manage their intents, dialogs, and knowledge bases, and run desks with sessions, conversations, routing, and campaigns.

Use for: Send a customer message to my Moveo virtual assistant, Get the transcript of yesterday's support session, Search the knowledge base for the refund policy, I need to add a new intent with example expressions

Not supported: Does not process payments, host phone numbers, or run a ticketing help center. Use for Moveo.AI conversational agents, desks, knowledge bases, and contacts only.

The Moveo.AI API builds, trains, and runs conversational AI agents, which Moveo calls brains, and connects them to channels such as Facebook, Viber, and a web widget. Brains are configured with intents, entities, dialogs, insights, webhooks, and a model strategy, then versioned, published, and retrained. Environments, called desks, hold sessions, conversations, routing rules, departments, SLAs, business hours, macros, and channel integrations for the live support team. Knowledge bases ingest documents from datasources and can be searched, while contacts, campaigns, and reports cover customer records, outbound messaging, and analytics.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

87%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

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

32%

Example Density

How richly the API is illustrated with examples.

99%

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

58%

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.

63%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

42%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

62%

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: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Moveo.AI to your agent

Capabilities

Start building with Moveo.AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Moveo.AI

Jentic AI Readiness Score

Moveo.AI

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