Install Jentic One Beta

Connect the MatuleApp API to your agent

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

Get and update a user profile

List products with search and get product details

Create and update a shopping cart

Create an order

GET STARTED

Start building with MatuleApp API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MatuleApp API for, with concrete tasks.

★ Product Browsing and Search

An AI agent connected through Jentic can help a shopper find items. It lists products with a search filter and returns product details, so an assistant can surface matching goods and describe them without a manual browse of the app.

Search the product list for a query and return the matching items with details

Cart and Checkout

Turning a selection into an order is the core of a shopping flow. The MatuleApp API creates and updates a cart and then creates an order, letting an agent assemble a basket and place the order on the shopper's behalf.

Create a cart, add items, and place an order

Account Management

Personalised shopping needs an account. The API registers and authenticates users and reads and updates profiles, so an agent can sign a user in and keep their profile details current before shopping.

Authenticate a user and update their profile details

Key Endpoints

14 endpoints — the matuleapp api powers the matule shopping application.

METHOD

PATH

DESCRIPTION

GET

/collections/products/records

List products with search

GET

/collections/products/records/{id_product}

Get product details

POST

/collections/cart/records

Create a cart

POST

/collections/orders/records

Create an order

POST

/collections/users/auth-with-password

Authenticate a user with a password

GET

/collections/products/records

List products with search

GET

/collections/products/records/{id_product}

Get product details

POST

/collections/cart/records

Create a cart

POST

/collections/orders/records

Create an order

POST

/collections/users/auth-with-password

Authenticate a user with a password

Why Jentic?

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

Setup

Wiring the MatuleApp API by hand means authenticating a user, capturing the JWT, and attaching it to every product, cart, and order call yourself. Through Jentic you install once, import MatuleApp from the API Directory, store the token once, and your agent calls the shopping operations directly.

Permission scoping

You choose which of the operations your agent may call. You might allow product browsing and cart building while blocking order creation and profile edits, so the agent can shop without committing a purchase.

Credential isolation

Your MatuleApp 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 'search products', and Jentic returns the matching MatuleApp operation with its input schema so the agent calls it with the right query.

FAQs

Specific to using MatuleApp API through Jentic.

What authentication does the MatuleApp API use?

It authenticates with an HTTP Bearer token that is a JWT. Your agent obtains the token by authenticating a user with a password, then sends it as a Bearer credential on each call. Through Jentic the credential is stored once, encrypted, by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.

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

Yes. You choose which operations the agent may call. You might allow product browsing and cart building while blocking order creation and profile edits, so the agent can shop without committing a purchase, with every call logged by your own instance.

Is there a MatuleApp MCP server?

You don't need an MCP server to give your agent the MatuleApp API. Jentic connects it directly from the API Directory: import it, store the token once, and your agent calls the product, cart, and order operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

What are the rate limits for the MatuleApp API?

The OpenAPI spec does not define rate limits. Check the MatuleApp documentation for any current limits before running high-volume product searches or order operations.

What can the MatuleApp API do?

It registers and authenticates users, reads and updates profiles, lists products with search and returns product details, manages a shopping cart, creates orders, and serves news, promotions, and project listings.

How do I place an order through Jentic?

Search Jentic by intent, for example 'create an order', and Jentic returns the matching MatuleApp operation with its input schema. Your agent supplies the cart contents and reads back the created order. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Matule Ru MatuleApp API

Name: MatuleApp API
Brand: MatuleApp API
Availability: InStock

Community OpenAPI document · agent-readyE CommerceOrder ManagementHTTP Bearer (JWT)14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Register and authenticate users, read and update profiles, browse and search products, manage a cart, and create orders. Authenticates with an HTTP Bearer token (a JWT).

Use for: Register a new user account, Authenticate a user with a password, Search the product catalogue for an item, Get the details of a product

Not supported: Does not settle payments or manage inventory pricing. Use the MatuleApp API for user accounts, product browsing, cart, and order creation only.

The MatuleApp API powers the Matule shopping application. It registers and authenticates users, reads and updates user profiles, lists products with search and returns product details, manages a shopping cart, creates orders, and serves news and project listings.

Jentic One on Github View OpenAPI Document

Connect the MatuleApp API to your agent

Capabilities

Start building with MatuleApp API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Matule Ru MatuleApp API