Install Jentic One Beta

Connect the SignatureAPI to your agent

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

Create an envelope

List envelopes

Retrieve an envelope

Update an envelope

Delete an envelope

GET STARTED

Start building with SignatureAPI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SignatureAPI API for, with concrete tasks.

★ Developer Tools Operations

Use the SignatureAPI to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including create an envelope, list envelopes, retrieve an envelope.

Call POST /v1/envelopes to create an envelope

Automated Deliverables Management

Automate deliverables operations by combining multiple SignatureAPI endpoints. Agents can list envelopes and then retrieve an envelope in a single workflow.

Call GET /v1/envelopes to list envelopes, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'create an envelope', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — electronic signature api for creating envelopes, managing documents, recipients, ceremonies, and deliverables.

METHOD

PATH

DESCRIPTION

POST

/v1/envelopes

Create an envelope

GET

/v1/envelopes

List envelopes

GET

/v1/envelopes/{envelope_id}

Retrieve an envelope

PATCH

/v1/envelopes/{envelope_id}

Update an envelope

DELETE

/v1/envelopes/{envelope_id}

Delete an envelope

POST

/v1/envelopes/{envelope_id}/cancel

Cancel an envelope

GET

/v1/envelopes/{envelope_id}/events

List envelope events

POST

/v1/envelopes/{envelope_id}/deliverables

Create a deliverable

POST

/v1/envelopes

Create an envelope

GET

/v1/envelopes

List envelopes

GET

/v1/envelopes/{envelope_id}

Retrieve an envelope

PATCH

/v1/envelopes/{envelope_id}

Update an envelope

DELETE

/v1/envelopes/{envelope_id}

Delete an envelope

POST

/v1/envelopes/{envelope_id}/cancel

Cancel an envelope

GET

/v1/envelopes/{envelope_id}/events

List envelope events

POST

/v1/envelopes/{envelope_id}/deliverables

Create a deliverable

Why Jentic?

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

Setup

Wiring SignatureAPI by hand means sending its X-API-Key header, pointing calls at https://api.signatureapi.com, and tracking envelope ids and their events yourself. Through Jentic you install once, import SignatureAPI from the API Directory, store the API key once, and your agent calls it.

Permission scoping

SignatureAPI puts the envelope id in the URL path (/v1/envelopes/{envelope_id}), so a rule can pin your agent to one envelope: it can read that envelope, its events, and its deliverables and nothing else. You choose the operations it may call, so destructive ones like deleting or cancelling an envelope are not included unless you add them.

Credential isolation

Your SignatureAPI 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 'create an envelope' or 'get envelope events', and Jentic returns the matching SignatureAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SignatureAPI API through Jentic.

What authentication does the SignatureAPI use?

The SignatureAPI uses an API key passed in the `X-API-Key` 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 create an envelope with the SignatureAPI?

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

What are the rate limits for the SignatureAPI?

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 an envelope through Jentic?

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

How many endpoints does the SignatureAPI have?

The SignatureAPI exposes 15 endpoints covering deliverables, envelopes, recipients operations.

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

Yes. Because you run Jentic One yourself and set the rules, you decide which SignatureAPI operations and credentials your agent may use. Since the envelope id sits in the URL path (/v1/envelopes/{envelope_id}), a rule can pin the agent to a single envelope so it only reads that envelope, its events, and its deliverables. Destructive operations such as deleting or cancelling an envelope stay off limits unless you explicitly allow them.

SignatureAPI

Name: SignatureAPI API
Brand: SignatureAPI
Availability: InStock

AI ReadinessAI-Ready (A-)75/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey15 EndpointsREST

For Agents

Programmatically create an envelope, list envelopes. Covers 15 operations with apiKey authentication.

Use for: I need to an envelope, I want to envelopes, Search for an envelope, Find all an envelope

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

Electronic signature API for creating envelopes, managing documents, recipients, ceremonies, and deliverables. The API exposes 15 endpoints secured with apiKey authentication.

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

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

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

72%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

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: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SignatureAPI to your agent

Capabilities

Start building with SignatureAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SignatureAPI

Jentic AI Readiness Score

SignatureAPI

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