canonical: https://jentic.com/apis/signicat.com/signicat

# Signicat API

Digital identity and electronic signing. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get access token, list resources. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Get access token |
| GET | `/resources` | List resources |
| GET | `/resources/{id}` | Get resource |

## Key resources

- **Authentication** — Authentication and authorization
- **Resources** — Resource management

## AI readiness

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.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 94 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/signicat.com/signicat/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

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

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

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