Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the databyte 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%2Fdatabyte.de%2Fdatabyte" | shStep 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%2Fdatabyte.de%2Fdatabyte" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with databyte REST-API.
Search the company database with detailed query options
Export company result sets and inspect their info and fill rate
Create, copy, rename, empty, and delete company lists
Add, remove, and read the data in a company list
Set up monitoring on company lists to track record changes
GET STARTED
Run DataMatch projects to reconcile your records against the database
Patterns agents use databyte REST-API for, with concrete tasks.
★ Agent-Driven Company Prospecting
An AI agent connected through Jentic can find and collect target companies without a human in the databyte frontend. It runs a company search with the required criteria, saves the matches into a company list, and exports the result set, so a sales or research workflow gets a ready list of German B2B companies to work from.
Search the database for companies matching an industry and region, add the matches to a new list, and export the result set
Record Reconciliation with DataMatch
Keeping an internal company list aligned with an authoritative database is tedious by hand. The databyte API's DataMatch flow creates a project, adds your records, starts the match, and returns the result, so an agent can reconcile a CRM's company records against databyte and flag mismatches for review.
Create a DataMatch project, add our company records, start it, and read back the match result
List Monitoring for Data Changes
Company details change, and stale records cost time. The databyte API sets and reads monitoring on a company list, so an agent can watch a saved list and surface when a monitored company's data has changed, keeping downstream records current.
Save monitoring on a company list and later read the monitoring results to find companies whose data changed
29 endpoints — the databyte rest-api exposes the databyte business engine, a german b2b company database, for direct integration without a web frontend.
METHOD
PATH
DESCRIPTION
/search/fi
Search the company database
/export
Export a company result set
/fls/create
Create a company list
/datamatch/create
Create a DataMatch reconciliation project
/datamatch/result
Read the DataMatch result
/search/fi
Search the company database
/export
Export a company result set
/fls/create
Create a company list
/datamatch/create
Create a DataMatch reconciliation project
/datamatch/result
Read the DataMatch result
What agents get from Jentic-routed access to this vendor.
Setup
Wiring databyte by hand means managing Basic auth credentials, tracking your data credit quota, and sequencing search, list, and DataMatch calls yourself. Through Jentic you install once, import databyte from the API Directory, store the credentials once, and your agent calls the operations directly.
Permission scoping
You choose which of the 29 operations your agent may call, so it can be bounded to exactly the work it needs. You might allow company search and list reading while blocking list deletion and credit reloads.
Credential isolation
Your databyte 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 the databyte company database', and Jentic returns the matching operation with its input schema so the agent calls it with the right query criteria.
Alternatives and complements available in the Jentic catalogue.
Specific to using databyte REST-API through Jentic.
What authentication does the databyte REST-API use?
The databyte REST-API uses HTTP Basic authentication, sending credentials in the Authorization header per its OpenAPI spec. Through Jentic those credentials are stored once by your own self-hosted instance and injected when the agent calls, so they never appear in the agent's prompt or logs.
Is there a databyte MCP server?
You don't need an MCP server to give your agent the databyte REST-API. Jentic connects it directly from the API Directory: import it, store your Basic credentials once, and your agent calls the search, list, and DataMatch operations. Operations are discovered on demand, so nothing extra loads into the agent's context.
Can I limit what my agent is allowed to do with the databyte REST-API?
Yes. You choose which of the 29 operations the agent may call, so it can be bounded to exactly the work it needs. You might allow company search and list reading while blocking list deletion and credit reloads, with every call logged.
How does DataMatch reconciliation work through the databyte API?
DataMatch is a four-step flow: the API creates a project, adds your records, starts the project, and returns the match result, with operations to list, abort, and clear projects. An agent can run the whole sequence to reconcile your records against the databyte database.
What are the rate limits for the databyte REST-API?
The OpenAPI spec does not specify rate limits, though usage is governed by a data credit quota you can read and reload through the API. Check the databyte documentation for current limits before running large exports or matches.
How do I search for companies through Jentic?
Search Jentic by intent, for example 'search the databyte company database', and Jentic returns the search operation with its input schema. Your agent supplies the query criteria and reads back the matching companies. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Search a German B2B company database, export result sets, manage company lists and monitoring, and run DataMatch reconciliation projects across 29 endpoints. Authenticates with HTTP Basic authentication.
Use for: Search the databyte database for companies matching criteria, Export a set of company records, Create a company list and add records to it, Set up monitoring on a company list
Not supported: Does not provide consumer or contact-level data, and does not run outreach or messaging. Use for German B2B company data search, lists, monitoring, and matching only.
The databyte REST-API exposes the databyte Business Engine, a German B2B company database, for direct integration without a web frontend. Across 29 endpoints it searches company records, exports and profiles result sets, manages company lists and their monitoring, tracks data credits, and runs DataMatch projects that reconcile your records against the database.