Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode

Install Jentic One Beta

Connect the SignRequest API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SignRequest 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.

1

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%2Fsignrequest.com%2Fsignrequest" | sh
2

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%2Fsignrequest.com%2Fsignrequest" | 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 SignRequest API.

Retrieve a list of API tokens

Create a Document Attachment

Search documents

Query and filter SignRequest API records by parameters

Monitor SignRequest API operational status and events

GET STARTED

Start building with SignRequest API

Explore with Jentic One
View OpenAPI Document

Use Cases

Patterns agents use SignRequest API for, with concrete tasks.

★ Developer Tools Operations

Use the SignRequest API to perform developer tools operations programmatically. The API provides 35 endpoints covering core functionality including retrieve a list of API tokens, retrieve a list of auditevents, create a document attachment.

Call GET /api-tokens to retrieve a list of API tokens

Automated api-tokens Management

Automate api-tokens operations by combining multiple SignRequest API endpoints. Agents can retrieve a list of auditevents and then create a document attachment in a single workflow.

Call GET /audit-events to retrieve a list of auditevents, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'retrieve a list of API tokens', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

35 endpoints — signrequest is a digital signature solution.

METHOD

PATH

DESCRIPTION

GET

/api-tokens

Retrieve a list of API tokens

GET

/audit-events

Retrieve a list of AuditEvents

POST

/document-attachments

Create a Document Attachment

GET

/document-attachments

Retrieve a list of Document Attachments

GET

/document-attachments/{uuid}

Retrieve a Document Attachment

GET

/documents-search

Search documents

POST

/documents

Create a Document

GET

/documents

Retrieve a list of Documents

GET

/api-tokens

Retrieve a list of API tokens

GET

/audit-events

Retrieve a list of AuditEvents

POST

/document-attachments

Create a Document Attachment

GET

/document-attachments

Retrieve a list of Document Attachments

GET

/document-attachments/{uuid}

Retrieve a Document Attachment

GET

/documents-search

Search documents

POST

/documents

Create a Document

GET

/documents

Retrieve a list of Documents

Why Jentic?

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

Setup

Wiring SignRequest by hand means putting its API key in the Authorization header, pointing calls at https://signrequest.com/api/v1, and tracking document and attachment uuids yourself. Through Jentic you install once, import SignRequest from the API Directory, store the API key once, and your agent calls it.

Permission scoping

SignRequest puts the attachment uuid in the URL path (/document-attachments/{uuid}), so a rule can pin your agent to one attachment: it can read that attachment and nothing else. You choose the operations it may call, so creating documents or attachments is not included unless you add it.

Credential isolation

Your SignRequest API 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 'search documents' or 'list audit events', and Jentic returns the matching SignRequest operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

→

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using SignRequest API through Jentic.

What authentication does the SignRequest API use?

The SignRequest API uses an API key passed 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 retrieve a list of API tokens with the SignRequest API?

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

What are the rate limits for the SignRequest 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 retrieve a list of API tokens through Jentic?

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

How many endpoints does the SignRequest API have?

The SignRequest API exposes 35 endpoints covering api-tokens, audit-events, document-attachments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SignRequest operations the agent may call and which stored credentials it may use. Since SignRequest puts the attachment uuid in the URL path (/document-attachments/{uuid}), a rule can pin the agent to a single attachment so it reads that one resource and nothing else. You choose the allowed operations, so write actions like creating documents (POST /documents) or attachments (POST /document-attachments) stay off limits unless you add them.

APIs / Developer Tools / SignRequest API
SignRequest API logo

SignRequest API

58
AI ReadinessFoundational (C+)58/100
See full scorecard
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey35 EndpointsREST

For Agents

Programmatically retrieve a list of API tokens, retrieve a list of auditevents. Covers 35 operations with apiKey authentication.

Use for: I need to a list of API tokens, I want to a list of auditevents, Search for a document attachment, Find all a list of document attachments

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

SignRequest is a digital signature solution. This API allows you to create and manage document signing requests. The API exposes 35 endpoints secured with apiKey authentication.

Jentic One on GithubView OpenAPI Document

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

S

SignRequest API

- Foundational (C+)
58/100
83
Foundational Compliance
56
Developer Experience & Jentic Compatibility
40
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
60
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
83

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

35%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

26%

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.

40

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4
27%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

74%

OperationId Quality

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

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

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.

50

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

60

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>