Install Jentic One Beta

Connect the neugeschaeft REST-API to your agent

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

Search roughly 11 million DACH company records with detailed or selection-list results

Export selected company records and read export info and fill-rate statistics

Create, copy, rename, and share company lists

Add and remove records in a company list and read them back

Monitor saved company lists for changes

GET STARTED

Start building with neugeschaeft REST-API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use neugeschaeft REST-API for, with concrete tasks.

★ AI Agent Company Lookup

An AI agent connected through Jentic finds companies that match a user's criteria across the DACH region and exports the matching records for downstream use. Detailed search returns full firmographic records, while the selection-list variant returns summarized matches when the agent only needs a shortlist.

Search for companies matching given criteria and export the matching records

List Building and Monitoring

A sales operation builds a company list, adds matching records, and sets up monitoring so changes to those companies are surfaced over time. Lists can be copied, renamed, and shared with colleagues, keeping a working set in one place.

Create a company list, add matching records, and set up monitoring for changes

Data Matching and Reconciliation

To clean a CRM, an agent runs a data-match project: it creates the project, adds the records to reconcile, starts the match, and reads the result against the database. This flags which of your records correspond to known companies.

Create a data-match project, add your records, start it, and read the match results

Key Endpoints

29 endpoints — the neugeschaeft rest-api provides programmatic access to a business database of roughly 11 million company records across the dach region.

METHOD

PATH

DESCRIPTION

POST

/search/fi

Search companies with detailed results

POST

/export

Export selected company records

GET

/export/info

Get export info

GET

/fls/list

List company lists

POST

/fls/create

Create a company list

POST

/datamatch/create

Create a data-match project

GET

/datamatch/result

Get data-match results

POST

/search/fi

Search companies with detailed results

POST

/export

Export selected company records

GET

/export/info

Get export info

GET

/fls/list

List company lists

POST

/fls/create

Create a company list

POST

/datamatch/create

Create a data-match project

GET

/datamatch/result

Get data-match results

Why Jentic?

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

Setup

Wiring the neugeschaeft REST-API by hand means setting up HTTP Basic authentication, tracking your query credits, and shaping each company search and export yourself. Through Jentic you install once, import neugeschaeft from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

neugeschaeft carries search criteria and list identifiers in the request body, so rules bound which operations your agent may call, not which lists it touches. You choose the operations it may use, such as searching and exporting records, so deleting or sharing a company list is not included unless you add it.

Credential isolation

Your neugeschaeft Basic auth credentials 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 'search company records' or 'export companies', and Jentic returns the matching neugeschaeft operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using neugeschaeft REST-API through Jentic.

What authentication does the neugeschaeft REST-API use?

It uses HTTP Basic authentication, as declared in its OpenAPI spec. You send your username and password with the request. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never appear in the agent's prompt or logs.

Can I search for companies in the DACH region with the neugeschaeft REST-API?

Yes. The company-search operation returns detailed records, a selection-list variant returns summarized matches, and you can export the results and read fill-rate statistics for the export.

What are the rate limits for the neugeschaeft REST-API?

The OpenAPI spec does not specify rate limits; usage is governed by the query credits on your account, which you can read through the credits operation. Check your neugeschaeft account for your current credit balance before running large exports.

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

Yes. Write a rule that allows only the search and export operations, so the agent can find and pull company records but cannot create, delete, or share company lists, and every call it makes is logged.

How do I search for companies with the neugeschaeft REST-API through Jentic?

Search Jentic for 'search company records', add the neugeschaeft REST-API from the directory, and store your Basic credentials once. Your agent runs the search and exports the matching records. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a neugeschaeft REST-API MCP server?

You don't need an MCP server to give your agent the neugeschaeft REST-API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the search, export, list, and data-match operations. That keeps extra tool definitions out of the agent's context.

Neugeschaeft De neugeschaeft REST-API

AI ReadinessNon-Ready (F)37/100

See full scorecard

Community OpenAPI document · agent-readyData EnrichmentCompany Databasic29 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search roughly 11 million DACH company records, export selected records, build and monitor company lists, and run data-match reconciliation projects.

Use for: Search for companies in the DACH region by criteria, Export a set of company records, Create a new company list, Add records to a company list

Not supported: Does not handle payments, email outreach, or CRM pipeline management. Use for company data search, export, and matching only.

The neugeschaeft REST-API provides programmatic access to a business database of roughly 11 million company records across the DACH region. It searches companies with detailed or selection-list results, exports selected records with fill-rate statistics, and builds and shares company lists. It also monitors lists for changes and runs data-match projects that reconcile your own records against the database.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

35%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

26%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

86%

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: FSignals: 1

10%

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

42%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the neugeschaeft REST-API to your agent

Capabilities

Start building with neugeschaeft REST-API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Neugeschaeft De neugeschaeft REST-API

Jentic AI Readiness Score

neugeschaeft 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