Install Jentic One Beta

Connect the Signaturit API to your agent

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

Count signature requests

Create a new signature request

List all signature requests

Get a specific signature request

Delete a signature request

GET STARTED

Start building with Signaturit API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Signaturit API for, with concrete tasks.

★ Communications Operations

Use the Signaturit API to perform communications operations programmatically. The API provides 52 endpoints covering core functionality including count signature requests, create a new signature request, list all signature requests.

Call GET /signatures/count.json to count signature requests

Automated Account Management

Automate account operations by combining multiple Signaturit API endpoints. Agents can create a new signature request and then list all signature requests in a single workflow.

Call POST /signatures.json to create a new signature request, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'count signature requests', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

52 endpoints — signaturit electronic signature api for creating and managing signature requests, certified emails, certified sms, templates, brandings, team management, and webhook subscriptions.

METHOD

PATH

DESCRIPTION

GET

/signatures/count.json

Count signature requests

POST

/signatures.json

Create a new signature request

GET

/signatures.json

List all signature requests

GET

/signatures/{id}.json

Get a specific signature request

DELETE

/signatures/{id}.json

Delete a signature request

POST

/signatures/{id}/reminder.json

Send signature reminder email

PATCH

/signatures/{id}/cancel.json

Cancel a signature request

GET

/signatures/{id}/documents/{documentId}/download/signed

Download signed document

GET

/signatures/count.json

Count signature requests

POST

/signatures.json

Create a new signature request

GET

/signatures.json

List all signature requests

GET

/signatures/{id}.json

Get a specific signature request

DELETE

/signatures/{id}.json

Delete a signature request

POST

/signatures/{id}/reminder.json

Send signature reminder email

PATCH

/signatures/{id}/cancel.json

Cancel a signature request

GET

/signatures/{id}/documents/{documentId}/download/signed

Download signed document

Why Jentic?

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

Setup

Wiring Signaturit by hand means learning its bearer token auth, choosing the live or sandbox host under https://api.signaturit.com/v3, and tracking signature request ids yourself. Through Jentic you install once, import Signaturit from the API Directory, store the token once, and your agent calls it.

Permission scoping

Signaturit puts the signature id in the URL path (/signatures/{id}), so a rule can pin your agent to one signature request: it can read it, download its signed documents, and send reminders and nothing else. You choose the operations it may call, so destructive ones like deleting or cancelling a request are not included unless you add them.

Credential isolation

Your Signaturit token 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 'count signature requests' or 'download a signed document', and Jentic returns the matching Signaturit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Signaturit API through Jentic.

What authentication does the Signaturit API use?

The Signaturit API uses a Bearer token in the Authorization 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 count signature requests with the Signaturit API?

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

What are the rate limits for the Signaturit 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 count signature requests through Jentic?

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

How many endpoints does the Signaturit API have?

The Signaturit API exposes 52 endpoints covering account, brandings, certified emails operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Signaturit operations and credentials the agent may use. Because Signaturit puts the signature id in the URL path (/signatures/{id}), you can pin the agent to a single signature request and grant only read, signed-document download, and reminder operations. Destructive calls like deleting or cancelling a request stay out of reach unless you explicitly add them.

Signaturit API

Name: Signaturit API
Brand: Signaturit API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer52 EndpointsREST

For Agents

Programmatically count signature requests, create a new signature request. Covers 52 operations with bearer authentication.

Use for: I need to count signature requests, I want to a new signature request, Search for all signature requests, Find all a specific signature request

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

Signaturit electronic signature API for creating and managing signature requests, certified emails, certified SMS, templates, brandings, team management, and webhook subscriptions. The API exposes 52 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

30%

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

29%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

Capabilities

Start building with Signaturit API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Signaturit API

Jentic AI Readiness Score

Signaturit 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