Install Jentic One Beta

Connect the Tadabase API to your agent

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

Check API Status

List All Tables

Create Record

Get Record

Update Record

Use Cases

Patterns agents use Tadabase API for, with concrete tasks.

GET STARTED

Start building with Tadabase API

Explore with Jentic One

View OpenAPI Document

Automated Records Management

Automate records operations by combining multiple Tadabase API endpoints. Agents can list all tables and then list table fields in a single workflow.

Call GET /data-tables to list all tables, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tadabase 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 apiKey tokens manually.

Search Jentic for 'check API status', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — tadabase rest api for viewing tables, fields and manipulating records.

METHOD

PATH

DESCRIPTION

GET

/status

Check API Status

GET

/data-tables

List All Tables

GET

/data-tables/{tableId}/fields

List Table Fields

POST

/data-tables/{tableId}/records

Create Record

GET

/data-tables/{tableId}/records

List Records

GET

/data-tables/{tableId}/records/{recordId}

Get Record

PUT

/data-tables/{tableId}/records/{recordId}

Update Record

DELETE

/data-tables/{tableId}/records/{recordId}

Delete Record

GET

/status

Check API Status

GET

/data-tables

List All Tables

GET

/data-tables/{tableId}/fields

List Table Fields

POST

/data-tables/{tableId}/records

Create Record

GET

/data-tables/{tableId}/records

List Records

GET

/data-tables/{tableId}/records/{recordId}

Get Record

PUT

/data-tables/{tableId}/records/{recordId}

Update Record

DELETE

/data-tables/{tableId}/records/{recordId}

Delete Record

Why Jentic?

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

Setup

Wiring the Tadabase API by hand means sending its TadabaseAuth header on every call and threading table and record ids through nested data-table routes yourself. Through Jentic you install once, import the Tadabase API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Tadabase puts the table id and record id in the URL path (/data-tables/{tableId}/records/{recordId}), so a rule can pin your agent to one table's records: it can read them and nothing else. You choose the operations it may call, so updating or deleting a record is not included unless you add it.

Credential isolation

Your Tadabase key 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 'list records in a table' or 'check API status', and Jentic returns the matching Tadabase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tadabase API through Jentic.

What authentication does the Tadabase API use?

The Tadabase API uses an API key passed in the `TadabaseAuth` header. 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.

Can I check API status with the Tadabase API?

Yes. Use the GET /status endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tadabase 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 check API status through Jentic?

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

How many endpoints does the Tadabase API have?

The Tadabase API exposes 8 endpoints covering records, status, tables operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tadabase operations and credentials the agent may use. Since Tadabase puts the table id and record id in the URL path (/data-tables/{tableId}/records/{recordId}), a rule can pin the agent to one table's records so it only reads them. You pick the operations it may call, so creating, updating, or deleting a record stays off limits unless you add it.

Tadabase API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey8 EndpointsREST

For Agents

Programmatically check API status, list all tables. Covers 8 operations with apiKey authentication.

Use for: I need to check API status, I want to all tables, Search for table fields, Find all record

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

Tadabase REST API for viewing tables, fields and manipulating records. Industry standard REST API for no-code database applications. The API exposes 8 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

50%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

62%

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

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tadabase API to your agent

Capabilities

Use Cases

Start building with Tadabase API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tadabase API

Jentic AI Readiness Score

Tadabase 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