Install Jentic One Beta

Connect the SignEasy API to your agent

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

Fetch user

Upload an original document

Delete an original

Create or send an envelope

Monitor SignEasy API operational status and events

Use Cases

GET STARTED

Start building with SignEasy API

Explore with Jentic One

View OpenAPI Document

Automated Embedded_Sending_Url Management

Automate embedded_sending_url operations by combining multiple SignEasy API endpoints. Agents can upload an original document and then fetch all originals in a single workflow.

Call POST /originals to upload an original document, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'fetch user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — signeasy api for electronic signature workflows including document upload, envelope creation, signing, templates, and embedded signing experiences.

METHOD

PATH

DESCRIPTION

GET

/user

Fetch user

POST

/originals

Upload an original document

GET

/originals

Fetch all originals

GET

/originals/{id}

Fetch an original

DELETE

/originals/{id}

Delete an original

POST

/envelopes

Create or send an envelope

GET

/envelopes

Fetch all envelopes

GET

/envelopes/{id}

Fetch an envelope

GET

/user

Fetch user

POST

/originals

Upload an original document

GET

/originals

Fetch all originals

GET

/originals/{id}

Fetch an original

DELETE

/originals/{id}

Delete an original

POST

/envelopes

Create or send an envelope

GET

/envelopes

Fetch all envelopes

GET

/envelopes/{id}

Fetch an envelope

Why Jentic?

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

Setup

Wiring SignEasy by hand means choosing between bearer token and OAuth2 authorization-code auth, pointing calls at https://api.signeasy.com/v3, and tracking original and envelope ids yourself. Through Jentic you install once, import SignEasy from the API Directory, store the credential once, and your agent calls it.

Permission scoping

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

Credential isolation

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

FAQs

Specific to using SignEasy API through Jentic.

What authentication does the SignEasy API use?

The SignEasy API uses bearer, oauth2 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 fetch user with the SignEasy API?

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

What are the rate limits for the SignEasy 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 fetch user through Jentic?

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

How many endpoints does the SignEasy API have?

The SignEasy API exposes 20 endpoints covering embedded_sending_url, embedded_signing_url, envelopes operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SignEasy operations and credentials the agent may use. Because SignEasy puts original and envelope ids in the URL path, such as /envelopes/{id}, you can pin the agent to a single envelope so it can read that one and nothing else. You also choose the operations it may call, so a destructive call like DELETE /originals/{id} is excluded unless you explicitly add it.

SignEasy API

Name: SignEasy API
Brand: SignEasy API
Availability: InStock

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject Storagebearer, oauth220 EndpointsREST

For Agents

Programmatically fetch user, upload an original document. Covers 20 operations with bearer, oauth2 authentication.

Use for: I need to fetch user, I want to upload an original document, Search for fetch all originals, Find all fetch an original

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

SignEasy API for electronic signature workflows including document upload, envelope creation, signing, templates, and embedded signing experiences. The API exposes 20 endpoints secured with bearer, 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).

75%

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

93%

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

63%

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.

57%

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

75%

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

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SignEasy API to your agent

Capabilities

Use Cases

Start building with SignEasy API

Key Endpoints

Why Jentic?

Related APIs

FAQs

SignEasy API

Jentic AI Readiness Score

SignEasy 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