Install Jentic One Beta

Connect the B2Brouter API to your agent

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

Create and send compliant electronic invoices for an account

Validate invoices and track their delivery and acknowledgement state

Import invoices from a file and attach supporting documents

Manage accounts, bank accounts, and tax report settings

Maintain client and provider contacts used on documents

GET STARTED

Start building with B2Brouter API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use B2Brouter API for, with concrete tasks.

★ Automated invoice issuance

A billing system needs to issue compliant electronic invoices and route them to recipients. The B2Brouter API creates an invoice under an account, validates it, and sends it through the e-invoicing network, returning delivery state for tracking.

Create an invoice via POST /accounts/{account}/invoices, then send it with POST /invoices/send_invoice/{id}

Invoice validation and compliance

Before an invoice is sent, it must pass structural and tax checks. The validate operation returns whether an invoice is well-formed so a backend can catch errors before transmission and generate tax reports.

Call GET /invoices/{id}/validate and, when valid, generate a tax report from the invoice

Contact and account management

A finance platform managing many billing entities needs to maintain accounts and their clients. The account and contact operations create accounts, configure bank accounts, and maintain client and provider contacts used on documents.

Create a contact via POST for an account and list its existing invoices

AI agent billing automation

An AI agent handling accounts receivable can draft, validate, and send invoices without hand-wiring the B2Brouter auth header. Through Jentic the agent discovers the invoicing operations by intent and calls them with the stored key.

Search Jentic for 'create and send an invoice', load the schema, and issue an invoice for a client

Key Endpoints

69 endpoints — the b2brouter api handles electronic invoicing and billing document exchange: creating, sending, validating, and tracking invoices and orders across accounts and contacts.

METHOD

PATH

DESCRIPTION

GET

/accounts/{account}/invoices

List the invoices for an account

POST

/accounts/{account}/invoices

Create an invoice under an account

GET

/invoices/{id}

Retrieve a single invoice

POST

/invoices/send_invoice/{id}

Send an invoice through the network

GET

/invoices/{id}/validate

Validate an invoice before sending

GET

/accounts/{account}/contacts

List the contacts for an account

GET

/accounts/{account}/invoices

List the invoices for an account

POST

/accounts/{account}/invoices

Create an invoice under an account

GET

/invoices/{id}

Retrieve a single invoice

POST

/invoices/send_invoice/{id}

Send an invoice through the network

GET

/invoices/{id}/validate

Validate an invoice before sending

GET

/accounts/{account}/contacts

List the contacts for an account

Why Jentic?

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

Setup

Wiring the B2Brouter API by hand means setting the X-B2B-API-Key header on every request and shaping the invoice, order, and contact payloads yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it.

Permission scoping

The B2Brouter API addresses invoices, orders, and contacts by id in the URL path, so you can limit the agent to the operations it needs, such as creating or validating an invoice. You credit the agent only with the operations you allow, so deleting an invoice stays out unless you add it.

Credential isolation

Your the B2Brouter 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 'create and send an invoice', and Jentic returns the matching B2Brouter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using B2Brouter API through Jentic.

What authentication does the B2Brouter API use?

The B2Brouter API authenticates with an API key sent in the X-B2B-API-Key header. Through Jentic the key is stored encrypted in your own instance and injected into each request at run time.

Is there a the B2Brouter API MCP server?

You don't need an MCP server to give your agent the B2Brouter API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec.

Can the B2Brouter API validate an invoice before sending it?

Yes. The GET /invoices/{id}/validate operation checks an invoice for structural and tax issues, so a backend can confirm it is well-formed before transmitting it through the e-invoicing network.

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

Yes. Because you run Jentic One yourself, your own rules decide which the B2Brouter API operations and credentials the agent may use. You grant only the operations it needs, such as creating and sending invoices, so deleting an account stays off limits unless you add it. The choice of what the agent may call is yours.

How do I connect my agent to the B2Brouter API through Jentic?

Search Jentic by intent such as 'create and send an invoice' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

B2Brouter API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Community OpenAPI document · agent-readyFinanceAccountingapiKey69 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create, send, validate, and track electronic invoices and orders, and manage the accounts and contacts they belong to.

Use for: I need to create an electronic invoice for a client, Send an invoice through the e-invoicing network, Validate an invoice before sending it, Import an invoice from a file

Not supported: Does not handle payment collection, payroll, or general ledger accounting - use for electronic invoicing and document exchange only.

The B2Brouter API handles electronic invoicing and billing document exchange: creating, sending, validating, and tracking invoices and orders across accounts and contacts. It supports tax report settings, attachments, and multiple document formats for compliant e-invoicing. Requests authenticate with an API key sent in the X-B2B-API-Key header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

89%

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).

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

58%

Example Density

How richly the API is illustrated with examples.

97%

Example Validity

Percentage of examples that conform to their schemas.

45%

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: C+Signals: 4

74%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

97%

OperationId Quality

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

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the B2Brouter API to your agent

Capabilities

Start building with B2Brouter API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

B2Brouter API

Jentic AI Readiness Score

B2Brouter 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