Install Jentic One Beta

Connect the Soda Cloud REST API to your agent

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

Create or update dataset data

Retrieve check results

Integrate Soda Cloud REST API into automated workflows

Query and filter Soda Cloud REST API records by parameters

Monitor Soda Cloud REST API operational status and events

GET STARTED

Start building with Soda Cloud REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Soda Cloud REST API for, with concrete tasks.

★ Developer Tools Operations

Use the Soda Cloud REST API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including create or update dataset data, retrieve check results.

Call POST /api/v1/datasets/{datasetId} to create or update dataset data

Data Retrieval and Monitoring

Query Soda Cloud REST 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 Soda Cloud REST API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Soda Cloud REST 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 'create or update dataset data', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — soda cloud rest api for managing datasets and retrieving check results.

METHOD

PATH

DESCRIPTION

POST

/api/v1/datasets/{datasetId}

Create or update dataset data

GET

/api/v1/checks

Retrieve check results

POST

/api/v1/datasets/{datasetId}

Create or update dataset data

GET

/api/v1/checks

Retrieve check results

Why Jentic?

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

Setup

Wiring the Soda Cloud REST API by hand means sending HTTP basic credentials on every request, choosing between the US and default cloud.soda.io hosts, and shaping the dataset payloads yourself. Through Jentic you install once, import the Soda Cloud REST API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Soda Cloud REST API puts the dataset id in the URL path (/api/v1/datasets/{datasetId}), so a rule can pin your agent to one dataset: it can update that dataset's data and nothing else. You choose the operations it may call, so reading checks is only included if you add it.

Credential isolation

Your Soda Cloud REST API 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 'update dataset data' or 'list quality checks', and Jentic returns the matching Soda Cloud REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Soda Cloud REST API through Jentic.

What authentication does the Soda Cloud REST API use?

The Soda Cloud REST 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.

Can I create or update dataset data with the Soda Cloud REST API?

Yes. Use the POST /api/v1/datasets/{datasetId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Soda Cloud REST 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 create or update dataset data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create or update dataset data'. Jentic returns the matching Soda Cloud REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Soda Cloud REST API have?

The Soda Cloud REST API exposes 2 endpoints covering datasets, checks operations.

Can I limit what my agent is allowed to do with the Soda Cloud REST API?

Yes. Because Jentic One is self-hosted, your own rules decide which Soda Cloud operations and credentials your agent may use. Since the dataset id sits in the URL path (POST /api/v1/datasets/{datasetId}), you can pin the agent to a single dataset so it updates that dataset's data and nothing else. You also choose the operations it may call, so reading check results via GET /api/v1/checks is included only if you add it.

Soda Cloud REST API

Name: Soda Cloud REST API
Brand: Soda Cloud REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbasic2 EndpointsREST

For Agents

Programmatically create or update dataset data, retrieve check results. Covers 2 operations with basic authentication.

Use for: I need to or update dataset data, I want to check results, Get the current status of Soda Cloud REST API resources, List all records from Soda Cloud REST API

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

Soda Cloud REST API for managing datasets and retrieving check results. Supports two cloud regions: EU (cloud.soda.io) and US (cloud.us.soda.io). The API exposes 2 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Soda Cloud REST API to your agent

Capabilities

Start building with Soda Cloud REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Soda Cloud REST API