Install Jentic One Beta

Connect the Bkper REST API to your agent

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

Set up double-entry books and their chart of accounts and groups

Record, post, check, and reconcile transactions in a book

Read account and group balances for a book

Organize books into collections and share them with collaborators

Run saved queries and attach files to a book

GET STARTED

Start building with Bkper REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Bkper REST API for, with concrete tasks.

★ Automate bookkeeping through Jentic

Let an agent record and post journal entries into a double-entry book without hand-wiring the OAuth2 flow. The agent records a transaction between two accounts and posts it so it affects the balances. Through Jentic the transaction operation is discovered by intent and called with its input schema, so entries land in the right book.

Record a transaction with POST /v5/books/{bookId}/transactions, then post it with PATCH /v5/books/{bookId}/transactions/post

Balance reporting

Pull up-to-date balances for a book to build a report or dashboard. The agent reads account and group balances for a book, so a finance workflow can reconcile figures or surface a trial balance on demand.

Read a book's balances with GET /v5/books/{bookId}/balances

Transaction search

Find specific transactions in a book using its query language. The agent lists transactions filtered by a query, so it can reconcile against a bank feed, flag unposted entries, or answer a question about a book's activity.

List transactions with GET /v5/books/{bookId}/transactions filtered by a query

Multi-user books

Give the right people access to a book without manual sharing. The agent adds a collaborator to a book and can list or remove collaborators, so onboarding a bookkeeper or accountant is scripted rather than clicked through.

Add a collaborator with POST /v5/books/{bookId}/collaborators

Key Endpoints

94 endpoints — the bkper rest api keeps double-entry books with their accounts, groups, transactions, and balances.

METHOD

PATH

DESCRIPTION

POST

/v5/books

Create a new book

GET

/v5/books/{bookId}/accounts

List a book's accounts

POST

/v5/books/{bookId}/transactions

Record a transaction

PATCH

/v5/books/{bookId}/transactions/post

Post a transaction

GET

/v5/books/{bookId}/balances

Get a book's balances

GET

/v5/books/{bookId}/transactions

List transactions in a book

POST

/v5/books/{bookId}/collaborators

Add a collaborator to a book

GET

/v5/user

Get the authenticated user

POST

/v5/books

Create a new book

GET

/v5/books/{bookId}/accounts

List a book's accounts

POST

/v5/books/{bookId}/transactions

Record a transaction

PATCH

/v5/books/{bookId}/transactions/post

Post a transaction

GET

/v5/books/{bookId}/balances

Get a book's balances

GET

/v5/books/{bookId}/transactions

List transactions in a book

POST

/v5/books/{bookId}/collaborators

Add a collaborator to a book

GET

/v5/user

Get the authenticated user

Why Jentic?

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

Setup

Wiring Bkper by hand means setting up a Google OAuth2 flow with the email scope, learning its book, account, and transaction model, and the post-and-check transaction lifecycle. Through Jentic you install once, import Bkper from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Bkper puts the book id in the URL path (/v5/books/{bookId}/...), so a rule can pin your agent to one book: it can record and read transactions for that book and nothing else. You choose which operations it may call, so deleting accounts or removing collaborators stays out unless you add them.

Credential isolation

Your Bkper credential 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 'record a transaction' or 'get a book's balances', and Jentic returns the matching Bkper operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Bkper REST API through Jentic.

What authentication does the Bkper REST API use?

The Bkper REST API authenticates with a Google OAuth2 access token carrying the email scope, sent as a bearer token, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I record and post transactions with the Bkper REST API?

Yes. Record a transaction between accounts in a book, then post it so it affects the balances, and check or trash it as the book is reconciled. Batch operations record or post many transactions in one request.

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

Yes. Bkper puts the book id in the URL path, so a rule can allow your agent to record and read transactions for one book while blocking account deletion or collaborator changes unless you add those operations. Every book keeps its own audit under your control.

What are the rate limits for the Bkper REST API?

The OpenAPI spec does not specify rate limits. Check the Bkper documentation at https://bkper.com/docs for current limits before running large batch jobs.

Is there a Bkper MCP server?

You don't need an MCP server to give your agent Bkper. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent runs the book, transaction, and balance operations on demand. That also keeps extra tool definitions out of the agent's context.

How do I record a transaction with the Bkper REST API through Jentic?

Search Jentic for 'record a transaction' and it returns the Bkper transaction operation with its input schema. Your agent records the transaction between two accounts and posts it so it hits the balances. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Bkper REST API

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceAccountingoauth294 EndpointsREST

For Agents

Keep double-entry books in Bkper: set up books and accounts, record and post transactions, read balances, run saved queries, and share books with collaborators across 94 endpoints.

Use for: Create a new book for a client's accounting, Record a transaction between two accounts, Post a pending transaction so it hits the balances, Get the current balances for a book

Not supported: Does not process payments, file taxes, or run payroll. Use for double-entry bookkeeping of books, accounts, and transactions only.

The Bkper REST API keeps double-entry books with their accounts, groups, transactions, and balances. It records transactions between accounts, posts and checks them as a book is reconciled, reads account and group balances, and runs saved queries over a book's entries. Books can be copied, audited, organized into collections, and shared with collaborators, and each book carries its own files, events, and integrations.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

75%

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: BSignals: 4

10%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

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

93%

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: B-Signals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

86%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

25%

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: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Bkper REST API to your agent

Capabilities

Start building with Bkper REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bkper REST API

Jentic AI Readiness Score

Bkper REST API

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