Install Jentic One Beta

Connect the Enterobase-API to your agent

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

Access Enterobase-API resources via REST API

Manage crm data programmatically

Integrate Enterobase-API into automated workflows

Query and filter Enterobase-API records by parameters

Monitor Enterobase-API operational status and events

GET STARTED

Start building with Enterobase-API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query Enterobase-API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Enterobase-API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Enterobase-API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'enterobase-api', load the operation schema, and execute with Jentic-managed credentials

Why Jentic?

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

Setup

Wiring the Enterobase API by hand means setting up HTTP basic auth against the enterobase.warwick.ac.uk/api/v2.0 host and attaching those credentials to every request yourself. Through Jentic you install once, import the Enterobase API from the API Directory, store the basic credentials once, and your agent calls it.

Permission scoping

The Enterobase API puts the database in the URL path (/api/v2.0/{database}/...), so a rule can pin your agent to one database. Its operations are read-oriented lookups, so you choose which the agent may call and it can query strains, assemblies and schemes for that database and nothing beyond the operations you allow.

Credential isolation

Your Enterobase basic 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 'look up strain data for a database' or 'fetch assemblies by barcode', and Jentic returns the matching Enterobase API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Enterobase-API through Jentic.

What authentication does the Enterobase-API use?

The Enterobase-API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

What are the rate limits for the Enterobase-API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I use enterobase-api through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use enterobase-api'. Jentic returns the matching Enterobase-API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Enterobase-API have?

The Enterobase-API exposes 30 endpoints covering v2.0 operations.

Does the Enterobase-API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Enterobase operations and credentials the agent may use. Since the Enterobase API puts the database in the URL path (/api/v2.0/{database}/...), you can pin the agent to a single database, and because its operations are read-oriented lookups, you choose which ones it may call. That lets the agent query strains, assemblies, and schemes for the database you allow and nothing beyond the operations you approve.

Warwick Enterobase-API

Name: Enterobase-API
Brand: Enterobase-API
Availability: InStock

CRMContact Managementbasic30 EndpointsREST

For Agents

Programmatically access Enterobase-API resources. Covers 30 operations with basic authentication.

Use for: I need to integrate with Enterobase-API, Find available crm operations, Get the current status of Enterobase-API resources, List all records from Enterobase-API

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

API for EnteroBase (https://enterobase.warwick.ac.uk/) EnteroBase is a user-friendly online resource, where users can upload their own sequencing data for de novo assembly by a stream-lined pipeline. The assemblies are used for calling MLST and wgMLST patterns, allowing users to compare their strains to publicly available genotyping data from other EnteroBase users, GenBank and classical MLST data. The API exposes 30 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document