Install Jentic One Beta

Connect the SATORI API to your agent

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

Create or update a customer

Delete a customer

Query and filter SATORI API records by parameters

Monitor SATORI API operational status and events

GET STARTED

Start building with SATORI API

Explore with Jentic One

View OpenAPI Document

Automated Customers Management

Automate customers operations by combining multiple SATORI API endpoints. Agents can create or update a customer and then delete a customer in a single workflow.

Call POST /customer/upsert.json to create or update a customer, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'register a new customer', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — satori marketing automation api for customer registration, upsert, and deletion.

METHOD

PATH

DESCRIPTION

POST

/customer/registration.json

POST

/customer/upsert.json

Create or update a customer

POST

/customer/delete.json

Delete a customer

POST

/customer/registration.json

POST

/customer/upsert.json

Create or update a customer

POST

/customer/delete.json

Delete a customer

Why Jentic?

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

Setup

Wiring the SATORI API by hand means posting customer records to its public v4 endpoints and handling the registration, upsert, and delete calls yourself. Through Jentic you install once, import the SATORI API from the API Directory, and your agent calls it.

Permission scoping

The SATORI API takes its customer details in the request body rather than the URL path, so you limit the agent to the operations it needs, such as registering or upserting a customer, and you leave out the delete operation unless you add it. Every operation the agent runs is one you chose.

Credential isolation

The SATORI API public endpoints take no credential, and Jentic executes the calls without placing any secret in the agent's prompt, logs, or context. Any configuration you do store is held encrypted by your own Jentic One instance and injected at execution time.

Intent-based discovery

Agents search Jentic by intent such as 'register a new customer' or 'upsert a customer record', and Jentic returns the matching SATORI API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SATORI API through Jentic.

What authentication does the SATORI API use?

The SATORI API uses no authentication. 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 register a new customer with the SATORI API?

Yes. Use the POST /customer/registration.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SATORI 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 register a new customer through Jentic?

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

How many endpoints does the SATORI API have?

The SATORI API exposes 3 endpoints covering customers operations.

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

Yes. Because you run Jentic One yourself, you decide which SATORI API operations the agent can call, so you can allow it to register a customer with POST /customer/registration.json and upsert one with POST /customer/upsert.json while leaving out the delete operation entirely. The delete call to POST /customer/delete.json is only available to the agent if you choose to add it. Every operation the agent runs is one you selected, and since these public endpoints take customer details in the request body, your rules govern exactly which calls it can make.

Satr Jp SATORI API

Name: SATORI API
Brand: SATORI API
Availability: InStock

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Community OpenAPI document · agent-readyMarketingMarketing Automationnone3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically register a new customer, create or update a customer. Covers 3 operations.

Use for: I need to register a new customer, I want to or update a customer, Search for a customer, List all records from SATORI API

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

SATORI marketing automation API for customer registration, upsert, and deletion. The API exposes 3 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

30%

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.

50%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SATORI API to your agent

Capabilities

Start building with SATORI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Satr Jp SATORI API

Jentic AI Readiness Score

SATORI 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