Install Jentic One Beta

Connect the SYNDUIT API to your agent

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

Verify OAuth token

Create a contact

List all contacts

Get a specific contact

Update a contact

GET STARTED

Start building with SYNDUIT API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SYNDUIT API for, with concrete tasks.

★ Payments Operations

Use the SYNDUIT API to perform payments operations programmatically. The API provides 16 endpoints covering core functionality including verify oauth token, create a contact, list all contacts.

Call GET /me to verify oauth token

Automated Auth Management

Automate auth operations by combining multiple SYNDUIT API endpoints. Agents can create a contact and then list all contacts in a single workflow.

Call POST /contacts to create a contact, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'verify oauth token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — synduit marketing automation api for managing contacts, tags, dynamic fields, and webhook subscriptions.

METHOD

PATH

DESCRIPTION

GET

/me

Verify OAuth token

POST

/contacts

Create a contact

GET

/contacts

List all contacts

GET

/contacts/{id}

Get a specific contact

PUT

/contacts/{id}

Update a contact

DELETE

/contacts/{id}

Delete a contact

GET

/dynamic-fields

List all dynamic fields

POST

/tags

Create a tag

GET

/me

Verify OAuth token

POST

/contacts

Create a contact

GET

/contacts

List all contacts

GET

/contacts/{id}

Get a specific contact

PUT

/contacts/{id}

Update a contact

DELETE

/contacts/{id}

Delete a contact

GET

/dynamic-fields

List all dynamic fields

POST

/tags

Create a tag

Why Jentic?

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

Setup

Wiring the SYNDUIT API by hand means implementing its OAuth2 authorization-code flow against api.synduit.com, exchanging codes for tokens and refreshing them, then shaping the contact and tag requests yourself. Through Jentic you install once, import SYNDUIT from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

SYNDUIT puts the contact id in the URL path (/contacts/{id}), so a rule can pin your agent to one contact: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.

Credential isolation

Your SYNDUIT OAuth2 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 'create a contact' or 'verify the OAuth token', and Jentic returns the matching SYNDUIT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SYNDUIT API through Jentic.

What authentication does the SYNDUIT API use?

The SYNDUIT API uses OAuth 2.0 for authorization. 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 verify oauth token with the SYNDUIT API?

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

What are the rate limits for the SYNDUIT 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 verify oauth token through Jentic?

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

How many endpoints does the SYNDUIT API have?

The SYNDUIT API exposes 16 endpoints covering auth, contacts, tags operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Synduit operations and credentials the agent may use. Because Synduit puts the contact id in the URL path (/contacts/{id}), you can pin the agent to a single contact so it only reads and updates that record. You also choose the operations it may call, so destructive endpoints like DELETE /contacts/{id} stay off limits unless you explicitly add them.

SYNDUIT API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingoauth216 EndpointsREST

For Agents

Programmatically verify oauth token, create a contact. Covers 16 operations with oauth2 authentication.

Use for: I need to verify oauth token, I want to a contact, Search for all contacts, Find all a specific contact

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

SYNDUIT marketing automation API for managing contacts, tags, dynamic fields, and webhook subscriptions. The API exposes 16 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 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).

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

51%

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.

67%

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: A+Signals: 1

90%

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 SYNDUIT API to your agent

Capabilities

Start building with SYNDUIT API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SYNDUIT API

Jentic AI Readiness Score

SYNDUIT 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