Cuentica API

Name: Cuentica API
Brand: Cuentica API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingapiKey20 EndpointsREST

For Agents

Manage Spanish accounting records — providers, customers, invoices, and expenses — on the Cuentica platform. Useful for AI agents that automate freelancer or small-business bookkeeping.

Install Jentic One Beta

Connect the Cuentica API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cuentica 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://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 Cuentica API.

Read company profile and invoicing series via GET /company and GET /company/serie

Create, update, and delete provider records via /provider operations

Create, update, and delete customer records via /customer operations

GET STARTED

Start building with Cuentica API

Explore with Jentic

View OpenAPI Document

The Cuentica API exposes the Spanish online accounting platform aimed at freelancers and small businesses (autonomos and pymes). It covers the core accounting entities of company profile and invoicing series, bank accounts, providers, customers, invoices, and expenses. The API is REST-style with JSON bodies and uses an X-AUTH-TOKEN header for authentication. Agents can read company configuration, manage CRM-style provider and customer records, and create or update invoices and expenses to keep books in sync with operational systems.

Use Cases

Patterns agents use Cuentica API for, with concrete tasks.

★ Automated Invoice Issuance from a CRM

An agent can listen for closed-won deals in a CRM and create the matching invoice in Cuentica. It looks up or creates the customer record via /customer, then posts the invoice via the /invoice endpoint with the right invoicing series from /company/serie. The result is books that stay in sync with sales without a human re-entering data.

Look up the customer with GET /customer filtered by NIF, then POST /invoice with the deal value and the correct invoicing series.

Receipt-to-Expense Capture

A bookkeeping agent can ingest receipts from email or a mobile app, extract the supplier, amount, and VAT with an LLM, then create or match the provider via /provider and post the expense via the /expense endpoints. This keeps expense records up to date without manual data entry, which is often the bottleneck for autonomos using Cuentica.

Match the supplier with GET /provider by name, create the provider via POST /provider if missing, then POST /expense with amount, date, and VAT.

Customer and Provider Master Data Sync

An agent can keep Cuentica's customer and provider lists in sync with another system of record such as a CRM or e-commerce platform. By calling GET /customer and GET /provider on a schedule and reconciling against the source system, the agent prevents duplicate records and broken invoices caused by mismatched NIFs.

Reconcile customers between the source CRM and Cuentica by calling GET /customer, comparing on NIF, and updating diffs via PUT /customer/{id}.

AI Agent Integration via Jentic

A bookkeeping agent can use Jentic to discover Cuentica operations rather than hand-coding twenty endpoints. It searches for an intent like 'create an invoice in Cuentica', loads the /invoice schema, and executes the call with the auth token managed by Jentic so the freelancer's accounting credentials never enter the agent context.

Use Jentic search for 'create an invoice in Cuentica' and execute the matching POST /invoice operation with the customer ID and line items.

Key Endpoints

20 endpoints — the cuentica api exposes the spanish online accounting platform aimed at freelancers and small businesses (autonomos and pymes).

METHOD

PATH

DESCRIPTION

GET

/company

Retrieve company business data

GET

/company/serie

Retrieve invoicing series

GET

/customer

List customers

GET

/provider

List providers

POST

/provider

Create a provider

PUT

/provider/{id}

Update a provider

DELETE

/provider/{id}

Delete a provider

GET

/company

Retrieve company business data

GET

/company/serie

Retrieve invoicing series

GET

/customer

List customers

GET

/provider

List providers

POST

/provider

Create a provider

PUT

/provider/{id}

Why Jentic?

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

Credential isolation

The Cuentica X-AUTH-TOKEN is stored encrypted in the Jentic MAXsystem vault. Jentic injects it into the request header at execution time so the agent's prompt and outputs never contain the raw token.

Intent-based discovery

Agents search Jentic by intent (for example 'create an invoice in Cuentica') and Jentic returns the matching operation with its input schema, so the agent does not need to read the Cuentica API documentation to choose between /invoice, /expense, and /customer.

Time to first call

Direct integration is two to three days to map twenty endpoints, handle the auth header, and reconcile customers and providers. Through Jentic the integration is under 30 minutes because each operation is a discoverable tool.

FAQs

Specific to using Cuentica API through Jentic.

What authentication does the Cuentica API use?

Cuentica uses an API key sent in the X-AUTH-TOKEN header on every request. Through Jentic the token is held in the encrypted MAXsystem vault and injected at request time, so a bookkeeping agent never sees the raw key.

Can I create an invoice with the Cuentica API?

Yes. POST /invoice creates a new invoice tied to a customer and an invoicing series. Look up the series with GET /company/serie and the customer with GET /customer first so the invoice attaches to the right entities.

What are the rate limits for the Cuentica API?

Cuentica does not publish specific rate limits in the OpenAPI spec. Cap automated batches at a few requests per second per token and back off on 429 responses to avoid being throttled.

How do I record a business expense with the Cuentica API through Jentic?

Run pip install jentic, search Jentic for 'record a business expense in Cuentica', load the schema for POST /expense, and execute it with the supplier ID, amount, and VAT. Jentic handles the X-AUTH-TOKEN header from your stored credentials.

How do I keep customer records in sync with Cuentica?

Call GET /customer to list current records, compare against your source system on NIF, and use POST /customer or PUT /customer/{id} to add or update entries. Avoid duplicate NIFs because invoices reference the customer ID.

Is the Cuentica API free?

The API is included with a paid Cuentica subscription. Cuentica plans are aimed at autonomos and small businesses in Spain, with pricing on cuentica.com rather than in the OpenAPI spec.

Cuentica API

Connect the Cuentica API to your agent

Capabilities

Start building with Cuentica API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs