Install Jentic One Beta

Connect the Send in APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Send in APIs, 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%2Fnetaccounting.hu%2Fnetaccounting" | 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%2Fnetaccounting.hu%2Fnetaccounting" | 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 Send in APIs.

Book an outgoing (ki) or incoming (be) invoice into NetAccounting as a szamla XML document and receive its iktatoszam registration number

Post journal entries for one or more dates, each row carrying a debit ledger, a credit ledger, and an amount, with a logType journal code

Import bank statement items against an accountNumber

Upload a document with a name and a documentType such as Bevétel, Kiadás, Bankkivonat, or Pénztár, plus an optional label and note

Use Cases

GET STARTED

Start building with Send in APIs

Explore with Jentic One

View OpenAPI Document

★ Agent posting invoices into a Hungarian ledger

A bookkeeping agent that receives invoices from a billing tool needs to book them in NetAccounting. Through Jentic the agent searches for 'book an invoice in NetAccounting', loads the bookInvoiceService operation with its input schema, sets direction to ki for outgoing or be for incoming, and posts the szamla XML. On success the response lists the iktatoszam NetAccounting generated for each invoice. The APIKey header value is attached by your own Jentic One instance at call time.

Call POST /bookInvoiceService/ki with an outgoing invoice in szamla XML and record the returned iktatoszam

Daily journal entries

An accountant automating recurring postings sends journal rows grouped by date. Each row names a debit ledger number, a credit ledger number, and an amount, with optional fields such as costCenter and partnerName, and the logType query parameter selects the journal from codes including 3, 4, and 20.

Call POST /journalService with logType 3 and a body for 2025-01-02 containing one row with debit '113', credit '112', and amount 12000

Bank statement import

Rather than keying bank lines by hand, a firm sends the statement for an account to NetAccounting with the account number and its transaction items. Supporting files such as the statement PDF can be registered separately with the document upload operation using the Bankkivonat document type.

Call POST /bank/import with accountNumber and the statement items, then POST /UploadService with name 'statement-2025-01' and documentType 'Bankkivonat'

Key Endpoints

4 endpoints — the send in apis push bookkeeping data into the hungarian netaccounting system: outgoing or incoming invoices as xml, journal entries grouped by date with debit and credit ledger numbers, bank statement items for an account number, and supporting documents labelled by type.

METHOD

PATH

DESCRIPTION

POST

/bookInvoiceService/{direction}

Book an incoming or outgoing invoice

POST

/journalService

Create journal entries for given dates

POST

/bank/import

Import bank statement items

POST

/UploadService

Upload one document

POST

/bookInvoiceService/{direction}

Book an incoming or outgoing invoice

POST

/journalService

Create journal entries for given dates

POST

/bank/import

Import bank statement items

POST

/UploadService

Upload one document

Why Jentic?

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

Setup

Wiring NetAccounting by hand means building szamla invoice XML, nesting journal rows under date and row-number keys, picking the right logType code, and adding the APIKey header to every call. Through Jentic you install once, import the Send in APIs from the API Directory, store the key once, and your agent calls it.

Permission scoping

NetAccounting puts the invoice direction in the URL path (/bookInvoiceService/ki or /be), so a rule can limit your agent to one direction, for example incoming invoices only. You choose the operations it may call, so journal posting or bank import is not included unless you add it.

Credential isolation

Your NetAccounting API key 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 'book an incoming invoice' or 'import a bank statement', and Jentic returns the matching NetAccounting operation with its input schema so the agent sends the right body format.

FAQs

Specific to using Send in APIs through Jentic.

What authentication do the NetAccounting Send in APIs use?

Per the OpenAPI spec, requests carry an API key in a header named `APIKey`. Through Jentic that key is stored encrypted by your own instance and added to each call, so it never appears in the agent's context.

Can I book both incoming and outgoing invoices?

Yes. POST /bookInvoiceService/{direction} takes direction ki for outgoing invoices or be for incoming ones, with the invoice in the szamla XML format. A successful booking returns the iktatoszam registration number NetAccounting assigned, and an error returns a hibakod element.

What are the rate limits for the NetAccounting Send in APIs?

The OpenAPI spec does not specify rate limits. Check https://netaccounting.hu or ask NetAccounting support for current limits before sending large journal or bank imports.

Is there a NetAccounting MCP server?

You don't need an MCP server to give your agent NetAccounting. Jentic connects it directly from the API Directory: import it, store your APIKey value once, and your agent calls the invoice, journal, bank, and document operations it needs.

How do I post a journal entry through Jentic?

Import the NetAccounting Send in APIs from the API Directory in your Jentic One instance and store your key. Your agent searches for 'post a journal entry', loads POST /journalService, and sends rows grouped by date with debit, credit, and amount, plus the logType query parameter. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the NetAccounting Send in APIs?

Yes. Write a rule that allows only POST /bookInvoiceService/be, and the agent can book incoming supplier invoices but cannot book outgoing ones, post journal entries, or import bank statements. Every call it makes is logged.

Netaccounting Hu Send in APIs

AI ReadinessFoundational (C-)50/100

See full scorecard

Community OpenAPI document · agent-readyFinanceAccountingapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Book incoming or outgoing invoices, post dated journal entries with debit and credit ledgers, import bank statement items, and upload typed documents into NetAccounting.

Use for: Book this outgoing invoice into NetAccounting, I need to record an incoming supplier invoice, Post a journal entry debiting ledger 113 and crediting 112 for 12000, Import last month's bank statement lines

Not supported: Does not issue invoices to customers, file tax returns, or read reports back out of the ledger. Use for sending bookkeeping data into NetAccounting only.

The Send in APIs push bookkeeping data into the Hungarian NetAccounting system: outgoing or incoming invoices as XML, journal entries grouped by date with debit and credit ledger numbers, bank statement items for an account number, and supporting documents labelled by type. A booked invoice returns the iktatoszam registration number NetAccounting generates on success. The spec's server is the NetAccounting test host, and the invoice XML follows the szamla schema that NetAccounting documents separately.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

11%

Example Density

How richly the API is illustrated with examples.

83%

Example Validity

Percentage of examples that conform to their schemas.

44%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

25%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

47%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Send in APIs to your agent

Capabilities

Use Cases

Start building with Send in APIs

Key Endpoints

Why Jentic?

Related APIs

FAQs

Netaccounting Hu Send in APIs

Jentic AI Readiness Score

Send in APIs

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness