Microsoftpichet Base Mandat

Name: Base Mandat API
Brand: Base Mandat
Availability: InStock

Browse all Swaggerhub Microsoftpichet APIs

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone2 Endpoints

Install Jentic One Beta

Connect the Base Mandat to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Base Mandat, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Base Mandat API.

Update progress of folder (signing, all signed, canceled)

Create a new sale

Integrate Base Mandat into automated workflows

Query and filter Base Mandat records by parameters

GET STARTED

Start building with Base Mandat API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically update progress of folder (signing, all signed, canceled), create a new sale. Covers 2 operations.

Use for: I need to progress of folder (signing, all signed, canceled), I want to a new sale, Get the current status of Base Mandat resources, List all records from Base Mandat

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Use Cases

Patterns agents use Base Mandat API for, with concrete tasks.

★ Developer Tools Operations

Use the Base Mandat to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including update progress of folder (signing, all signed, canceled), create a new sale.

Call POST /docapost-folder/update to update progress of folder (signing, all signed, canceled)

Data Retrieval and Monitoring

Query Base Mandat resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Base Mandat endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Base Mandat endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'update progress of folder (signing, all signed, canceled)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — api for pichet base mandat.

METHOD

PATH

DESCRIPTION

POST

/docapost-folder/update

Update progress of folder (signing, all signed, canceled)

POST

/sales

Create a new sale

POST

/docapost-folder/update

Update progress of folder (signing, all signed, canceled)

POST

/sales

Create a new sale

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any access details for Base Mandat are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'update a signing folder' or 'record a sale', and Jentic returns the matching Base Mandat operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Base Mandat API through Jentic.

What authentication does the Base Mandat use?

The Base Mandat uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I update progress of folder (signing, all signed, canceled) with the Base Mandat?

Yes. Use the POST /docapost-folder/update endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Base Mandat?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I update progress of folder (signing, all signed, canceled) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update progress of folder (signing, all signed, canceled)'. Jentic returns the matching Base Mandat operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Base Mandat have?

The Base Mandat exposes 2 endpoints covering docapost-folder, sales operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Base Mandat operations and credentials the agent may use. This API has just two operations, POST /docapost-folder/update to advance a signing folder and POST /sales to record a sale, and it carries its folder and sales targets in the request body rather than the URL path. You can scope the agent to only the operation it needs, such as recording a sale, so the folder-update path is not available unless you add it.