Install Jentic One Beta

Connect the MotionTools API to your agent

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

Sign users in via /auth/signin and refresh tokens via /auth/refresh

Create and update delivery bookings through the /bookings endpoints

Group bookings into tours and assign them to drivers via the /tours endpoints

Manage drivers, organisations, and services for a tenant

Read and update tenant customisations via /api/tenant/customizations

GET STARTED

Start building with MotionTools API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MotionTools API for, with concrete tasks.

★ Branded Last-Mile Delivery Operations

Retailers running their own last-mile fleet use MotionTools to ingest bookings from their storefront, group them into tours, and dispatch them to drivers. The API authenticates dispatchers via /auth/signin, creates bookings through the /bookings endpoints, and assembles tours via /tours. This replaces ad-hoc dispatcher tooling with an API-driven workflow.

Sign in via /auth/signin, create a booking with pickup and dropoff addresses via the /bookings endpoint, then attach it to an open tour via /tours.

Driver and Service Catalogue Management

Operations teams keep their MotionTools drivers, services, and capabilities in sync with HR and product changes. The API lets agents add new drivers, update service definitions, and adjust capabilities so the dispatch logic always reflects the live operating constraints. This avoids drift between the platform and the back-office systems of record.

List drivers via the /users endpoints filtered by driver role, then update their organisation assignment for a new shift pattern.

Tenant Customisation Read-and-Write

Multi-brand operators maintain separate customisations per tenant - branding, supported services, capabilities. The /api/tenant/customizations endpoint exposes those settings so an admin agent can read the current state and apply diffed updates programmatically. This keeps onboarding of new tenants scriptable.

Read /api/tenant/customizations, modify the branding fields, and write the updated payload back to apply changes.

Dispatch Agent via Jentic

An AI dispatch agent that needs to create a delivery for a new order searches Jentic for the booking creation operation, loads the input schema, and executes. Jentic injects the bearer token, so the agent never has the user's MotionTools credentials in context. The same agent can then attach the booking to a tour via a follow-up Jentic call.

Search Jentic for 'create a MotionTools delivery booking', load the /bookings operation, and execute it with the order's pickup and dropoff payload.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/auth/signin

Sign a user in and receive a bearer token

POST

/auth/refresh

Refresh an access token

POST

/auth/signout

Sign the current user out

GET

/account

Read the authenticated account

GET

/profile

Read the authenticated user's profile

GET

/users

List users in the tenant

GET

/organizations

List organisations under the tenant

GET

/api/tenant/customizations

Read tenant customisations

POST

/auth/signin

Sign a user in and receive a bearer token

POST

/auth/refresh

Refresh an access token

POST

/auth/signout

Sign the current user out

GET

/account

Read the authenticated account

GET

/profile

Read the authenticated user's profile

GET

/users

List users in the tenant

GET

/organizations

List organisations under the tenant

GET

/api/tenant/customizations

Read tenant customisations

Why Jentic?

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

Setup

Wiring MotionTools by hand means calling /auth/signin for a bearer, refreshing it at /auth/refresh, and mapping delivery, booking, and driver actions across its endpoints. Through Jentic you install once, import the MotionTools API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

MotionTools carries its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as reading the account, profile, or organizations. You choose the operations it may call, so sign-out is not included unless you add it.

Credential isolation

Your MotionTools sign-in credentials are stored once, encrypted, by your own Jentic One instance and exchanged for the short-lived bearer at execution time. The raw password never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a delivery booking' or 'assign a tour to a driver', and Jentic returns the matching MotionTools operation with its input schema, so the agent picks the right endpoint without browsing the docs.

FAQs

Specific to using MotionTools API through Jentic.

Why is there no official OpenAPI spec for MotionTools API?

MotionTools does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MotionTools 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 MotionTools API use?

MotionTools uses bearer authentication. Sign in via /auth/signin to receive an access token, refresh via /auth/refresh, and sign out via /auth/signout. Through Jentic, sign-in credentials live in the encrypted vault and only the bearer token reaches the agent context.

Can I create a delivery booking via the MotionTools API?

Yes. The /bookings endpoints support creating, listing, updating, and cancelling bookings, with pickup and dropoff details, services, and capability requirements specified in the request body.

What are the rate limits for the MotionTools API?

MotionTools does not publish hard limits in the spec. Cache the bearer token returned by /auth/signin for its lifetime and use /auth/refresh rather than re-signing in on every request.

How do I create a delivery through Jentic?

Run pip install jentic, search 'create a MotionTools delivery booking', load the /bookings operation, and execute it with pickup and dropoff details. Jentic supplies the bearer token from your vault.

Is the MotionTools API free?

API access is part of the MotionTools subscription, priced per workspace and active driver. Contact MotionTools for current pricing tiers.

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

Yes. Because you run Jentic One yourself, your own rules decide which MotionTools operations and credentials the agent may use, so you can grant only the calls it needs, such as reading the account, profile, or organizations while withholding booking, tour, or driver writes. MotionTools carries its targets in the request body rather than the URL path, so scoping happens at the operation level: you pick the exact endpoints the agent can reach. Sign-out is not included unless you explicitly add it, and the stored sign-in credentials are only ever exchanged for the short-lived bearer token at execution time.

MotionTools API

Name: MotionTools API
Brand: MotionTools API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticE CommerceShipping Logisticsbearer38 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage delivery logistics through MotionTools - authenticate users, create bookings, build tours, and configure drivers, services, and organisations.

Use for: I need to sign a user into MotionTools and get a bearer token, Create a delivery booking with pickup and dropoff addresses, Assign a booking to an active tour for a driver, List all drivers attached to an organisation

Not supported: Does not handle payment processing, vehicle telematics, or marketing campaigns - use for delivery logistics, bookings, tours, and driver management only.

Jentic publishes the only available OpenAPI specification for MotionTools API, keeping it validated and agent-ready. MotionTools is a delivery logistics platform that powers branded courier and last-mile operations for retailers and operators. The API exposes 38 endpoints covering authentication, user and driver management, organisations, services and capabilities, bookings, tours, tenant configuration, and file uploads. Authentication uses bearer tokens issued via the /auth/signin and /auth/refresh endpoints.

Jentic One on Github View OpenAPI Document

Connect the MotionTools API to your agent

Capabilities

Start building with MotionTools API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MotionTools API