Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationapiKey3 EndpointsREST
For Agents
Programmatically get access token, list resources. Covers 3 operations with apiKey authentication.
Use for: I need to access token, I want to resources, Search for resource, List all records from Signicat API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Digital identity and electronic signing. The API exposes 3 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Signicat API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Signicat 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%2Fsignicat.com%2Fsignicat" | sh2
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%2Fsignicat.com%2Fsignicat" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Signicat API.
Get access token
List resources
Integrate Signicat API into automated workflows
Query and filter Signicat API records by parameters
Monitor Signicat API operational status and events
Use Cases
Patterns agents use Signicat API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Signicat API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including get access token, list resources, get resource.
Call POST /auth/token to get access token
Automated Authentication Management
Automate authentication operations by combining multiple Signicat API endpoints. Agents can list resources and then get resource in a single workflow.
Call GET /resources to list resources, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Signicat 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 'get access token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — digital identity and electronic signing.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Get access token
GET
/resources
List resources
GET
/resources/{id}
Get resource
POST
/auth/token
Get access token
GET
/resources
List resources
GET
/resources/{id}
Get resource
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
Signicat API
- AI-Aware (B)64/100
94
Foundational Compliance58
Developer Experience & Jentic Compatibility45
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
94
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
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.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
33%
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.
45
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.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Signicat by hand means sending its X-API-Key header, pointing calls at https://api.signicat.com, and exchanging for an access token before reading resources. Through Jentic you install once, import Signicat from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Signicat puts the resource id in the URL path (/resources/{id}), so a rule can pin your agent to one resource: it can read that resource and nothing else. You choose the operations it may call, so token issuance is not included unless you add it.
Credential isolation
Your Signicat 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 'get an access token' or 'read a resource', and Jentic returns the matching Signicat 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.
FAQs
Specific to using Signicat API through Jentic.
What authentication does the Signicat API use?
The Signicat API 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 get access token with the Signicat API?
Yes. Use the POST /auth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Signicat 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 get access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching Signicat API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Signicat API have?
The Signicat API exposes 3 endpoints covering authentication, resources operations.
Can I limit what my agent is allowed to do with the Signicat API?
Yes. Because Jentic One is self-hosted, your own rules decide which Signicat operations and credentials your agent may use. Signicat puts the resource id in the URL path (/resources/{id}), so a rule can pin the agent to a single resource, letting it read that one resource with GET /resources/{id} and nothing else. You choose which operations it may call, so token issuance through POST /auth/token stays excluded unless you add it.
GET STARTED