Install Jentic One Beta

Connect the Cleansify API to your agent

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

Clean and normalise inbound records through POST /clean

Validate records against a configured rule set via POST /validate

Return structured change reports alongside cleaned payloads

Process both single records and batches in a single request

Authenticate per-request with an API key in the Authorization header

GET STARTED

Start building with Cleansify API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cleansify API for, with concrete tasks.

★ Lead capture cleansing before CRM ingestion

Marketing forms collect noisy data - extra whitespace, mixed-case emails, malformed phone numbers - that pollutes the CRM if pushed in raw. POST /clean normalises the record so the CRM sees a canonical version, and POST /validate flags records that should be rejected before insert. This pattern keeps duplicate detection accurate and reduces support tickets caused by bad contact data.

On every form webhook, call POST /clean with the submitted record and only forward the cleaned response to HubSpot if POST /validate returns no rule failures

ETL pipeline pre-load validation

Batch ETL jobs that ingest CSV or warehouse extracts use POST /validate as a gate step before loading into the warehouse. Records that fail are quarantined for manual review while passing records continue down the pipeline. This prevents bad data from entering the warehouse in the first place and shifts data quality left.

For each row in the nightly extract, call POST /validate and write failed rows to the quarantine S3 bucket while passing rows continue to the warehouse load step

AI agent integration via Jentic

An ops agent built on Jentic can clean a record on demand when a user pastes data into chat. The agent searches Jentic for the cleansing operation, loads the schema, and executes against POST /clean - returning a tidy version to the user. Because the API key is held in your Jentic One instance, multiple users can call the agent without each having their own credential.

Receive a CSV row pasted in chat, search Jentic for 'clean a data record', and execute POST /clean to return the normalised version

Key Endpoints

2 endpoints — cleansify is a data cleaning and validation service exposed through a small, focused rest api.

METHOD

PATH

DESCRIPTION

POST

/clean

Clean and validate input data

POST

/validate

Validate data against configured rules

POST

/clean

Clean and validate input data

POST

/validate

Validate data against configured rules

Why Jentic?

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

Setup

Wiring Cleansify by hand means passing its API key in the Authorization header on every call to api.cleansify.ai for its clean and validate operations. Through Jentic you install once, import Cleansify from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which Cleansify operations the agent may call, so you can limit it to the operations it needs, such as validate only, and leave clean out of the allowed set unless you add it.

Credential isolation

Your Cleansify API 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 'clean this data' or 'validate an input with Cleansify', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cleansify API through Jentic.

What authentication does the Cleansify API use?

Cleansify uses an API key passed in the Authorization header (the spec declares an apiKey scheme named 'Authorization' in the header). Through Jentic, the key is stored in the encrypted vault and applied at execution time, so agents never hold the raw key.

What is the difference between POST /clean and POST /validate?

POST /clean returns a normalised version of the input, with structured information about what was changed. POST /validate runs the input through a configured rule set and returns whether each record passes or fails along with the failing rules. Use /clean when you want corrected output and /validate when you want a pass/fail gate.

Can the Cleansify API process records in batches?

Yes - both POST /clean and POST /validate accept batched payloads, so a single request can cover a window of records rather than one row per call. This is the practical pattern for ETL gating where round-trip latency matters.

How do I add Cleansify as a step in my ETL through Jentic?

Install the SDK with pip install jentic, search Jentic for 'validate data records', load the returned schema, and call POST /validate at the gate stage of your pipeline. Failed records can then be routed to quarantine while passing rows continue downstream.

Does Cleansify expose validation rule configuration through the API?

The published OpenAPI surface covers only /clean and /validate operations; rule configuration is managed in the Cleansify dashboard rather than via API. Agents call /validate against the rule set already configured for the account.

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

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which Cleansify operations the agent may call, so you can allow POST /validate as a read-only pass/fail gate while leaving POST /clean out of the allowed set unless you add it. Your Cleansify API key is stored once and injected only at execution time, so it never enters the agent's prompt or logs, and the agent can only invoke the operations you have explicitly permitted.

Cleansify API

Name: Cleansify API
Brand: Cleansify API
Availability: InStock

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Clean and validate inbound records against rules with a single POST call. Useful for ETL hygiene, lead deduplication, and pre-database validation in data pipelines.

Use for: I need to clean a batch of leads before importing into the CRM, Validate a customer record against our data rules, Check whether the imported CSV passes validation, Run normalisation on inbound form submissions

Not supported: Does not handle email-specific deliverability scoring, address geocoding, or company firmographic enrichment - use for generic record cleaning and rule-based validation only.

Cleansify is a data cleaning and validation service exposed through a small, focused REST API. The API accepts records and either runs them through cleaning logic that normalises and corrects values, or validates them against a configured rule set. Both operations return the cleaned or validated payload along with structured information about what changed or what failed validation. It is designed to slot into ETL pipelines, lead-capture flows, or any workflow that needs deterministic data hygiene before persistence.

Jentic One on Github View OpenAPI Document

Connect the Cleansify API to your agent

Capabilities

Start building with Cleansify API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cleansify API