Install Jentic One Beta

Connect the Evoliz API to your agent

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

Authenticate against /api/login to obtain a bearer token for subsequent calls

List the companies attached to the authenticated Evoliz account

Manage clients per company via /api/v1/companies/{companyId}/clients

Track deliveries linked to invoices and orders via /api/v1/companies/{companyId}/deliveries

Record and reconcile payments via /api/v1/companies/{companyId}/payments

GET STARTED

Start building with Evoliz API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Evoliz API for, with concrete tasks.

★ Multi-Company Invoice Operations

Accountants who manage several SARLs, micro-entreprises, or holding structures juggle different VAT rules and branding per entity. The /api/v1/companies/{companyId}/* path family scopes every Evoliz call to one company, so an agent can iterate across the company list and apply per-entity actions (create clients, record payments) without mixing data between books.

GET /api/v1/companies, then for each companyId POST /api/v1/companies/{companyId}/clients with the new client payload

Payment Reconciliation

Finance teams reconcile bank receipts against issued invoices nightly. The Evoliz payments endpoint accepts payment records linked to a company, letting an agent ingest a bank statement, match each receipt against an Evoliz invoice, and POST the reconciled payment so the ledger updates without manual spreadsheet work.

Read the day's bank statement, match each receipt to an open invoice, and POST /api/v1/companies/{companyId}/payments for each matched receipt

Branded PDF Configuration

Boutique firms tailor invoice PDFs per company brand - logo, colour, payment instructions, mandatory legal mentions. The PDF settings endpoint lets an agent push that configuration programmatically when onboarding a new entity, so the first invoice issued already matches the brand without manual UI configuration.

PATCH /api/v1/companies/{companyId}/settings/pdf with the new logo URL and accent colour after onboarding a new client company

AI Bookkeeper via Jentic

An AI bookkeeping assistant inside a French SME drafts client records and books payments inside Evoliz from chat instructions. Jentic exposes Evoliz's bearer-secured endpoints as MCP tools so the agent searches by intent and executes per-company calls without staff ever leaving the chat.

Use Jentic search 'record an evoliz payment' to find POST /api/v1/companies/{companyId}/payments, load schema, and execute on bank-receipt events

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/login

Issue a bearer token

GET

/api/v1/companies

List companies

GET

/api/v1/companies/{companyId}/clients

List clients of a company

GET

/api/v1/companies/{companyId}/deliveries

List deliveries

GET

/api/v1/companies/{companyId}/payments

List payments

GET

/api/v1/companies/{companyId}/settings/pdf

Read PDF settings

POST

/api/login

Issue a bearer token

GET

/api/v1/companies

List companies

GET

/api/v1/companies/{companyId}/clients

List clients of a company

GET

/api/v1/companies/{companyId}/deliveries

List deliveries

GET

/api/v1/companies/{companyId}/payments

List payments

GET

/api/v1/companies/{companyId}/settings/pdf

Read PDF settings

Why Jentic?

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

Setup

Wiring the Evoliz API by hand means calling its /api/login to mint a bearer token, refreshing it, pointing at the www.evoliz.io host, and coding the per-company client, delivery, and payment reads yourself. Through Jentic you install once, import the Evoliz API from the API Directory, store the credentials once, and your agent calls it while Jentic refreshes the bearer for you.

Permission scoping

Evoliz puts the company id in the URL path (/api/v1/companies/{companyId}/clients), so a rule can pin your agent to one company: it can read that company's clients, deliveries, payments, and PDF settings and nothing else. You choose the operations it may call, so the agent only gets the ones you place in the allowed set.

Credential isolation

Your Evoliz login credentials and bearer token 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 'list evoliz clients' or 'read company payments', and Jentic returns the matching Evoliz operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Evoliz API through Jentic.

Why is there no official OpenAPI spec for Evoliz API?

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

Evoliz uses HTTP bearer tokens issued by POST /api/login. Through Jentic, login credentials sit in your Jentic One instance and Jentic refreshes the bearer token transparently so the agent only sees scoped execution rights.

Can I record a payment against an invoice with the Evoliz API?

Yes. POST /api/v1/companies/{companyId}/payments with the payment payload referencing the invoice ID. Evoliz reconciles the payment to the invoice in the ledger automatically.

What are the rate limits for the Evoliz API?

The OpenAPI spec does not declare specific rate limits; Evoliz applies plan-based throttling. Inspect 429 responses and Retry-After headers and confirm your account ceiling with Evoliz support before high-volume reconciliations.

How do I list a company's clients through Jentic?

Run pip install jentic, then await client.search('list evoliz clients'), client.load, client.execute. Jentic returns GET /api/v1/companies/{companyId}/clients with the companyId path parameter wired into the input schema.

Can I configure invoice PDF branding via the Evoliz API?

Yes. The /api/v1/companies/{companyId}/settings/pdf endpoint exposes per-company PDF configuration so an agent can push logo, accent colour, and template choices without using the Evoliz web UI.

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

Yes. Because Evoliz puts the company id in the URL path, such as /api/v1/companies/{companyId}/clients, a rule in your self-hosted Jentic One can pin your agent to a single company so it only reads that company's clients, deliveries, payments, and PDF settings and nothing else. You decide which operations sit in the allowed set, so the agent can call GET /api/v1/companies/{companyId}/payments without also being able to POST new payments unless you permit it. The rules and stored credentials live in your own instance, so the agent only ever gets the scoped operations you grant.

Evoliz API

Name: Evoliz API
Brand: Evoliz API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticFinanceAccountingbearer10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage Evoliz companies, clients, deliveries, payments, and PDF settings via 10 bearer-token-secured endpoints scoped to a company ID.

Use for: I need to log in to Evoliz and obtain a bearer token, List the companies under my Evoliz account, Create a new client in a specific Evoliz company, Record a payment against an invoice

Not supported: Does not handle payroll, inventory, or general-ledger journal entries - use for client, delivery, payment, and PDF-settings operations within Evoliz only.

Jentic publishes the only available OpenAPI specification for Evoliz API, keeping it validated and agent-ready. Evoliz is a French accounting and invoicing platform whose API exposes 10 endpoints for managing companies, clients, deliveries, payments, and PDF settings. Operations are scoped under /api/v1/companies/{companyId}/* so each request targets a specific accounting entity, with bearer-token authentication issued via /api/login.

Jentic One on Github View OpenAPI Document