canonical: https://jentic.com/apis/swaggerhub.siegmergius/authenticate

# Siegmergius Authenticate

Authenticate service allows users to login using their credentials. The API exposes 2 endpoints.

## For AI agents

Programmatically authenticateuser, deleteauthentication. Covers 2 operations.

## Scope

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

## Capabilities

- authenticateUser
- deleteAuthentication
- Integrate Authenticate into automated workflows
- Query and filter Authenticate records by parameters
- Monitor Authenticate operational status and events

## Use cases

### Identity and Authentication Operations

Use the Authenticate to perform identity auth operations programmatically. The API provides 2 endpoints covering core functionality including authenticateuser, deleteauthentication.

Example prompt: Call POST /authenticate/openid to authenticateuser

### Data Retrieval and Monitoring

Query Authenticate resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Authenticate endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /authenticate/openid | authenticateUser |
| DELETE | /authenticate/openid | deleteAuthentication |

## Key resources

- **authenticate** — Operations related to authenticate

## Why Jentic

- **Setup:** Wiring the Authenticate endpoints by hand means reading the onskyline.io docs, targeting that host, and writing your own OpenID request and retry handling even though the endpoints are open. Through Jentic you install once, import Authenticate from the API Directory, store any needed access detail once, and your agent calls it.
- **Permission scoping:** This API works through OpenID operations rather than a resource id in the path, so you limit the agent to the operations it needs, such as starting an OpenID session. You choose the operations it may call, so the DELETE that ends a session is not included unless you add it.
- **Credential handling:** Any Authenticate access detail 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 'start an OpenID login' or 'end an OpenID session', and Jentic returns the matching Authenticate 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 Authenticate use?

The Authenticate uses no 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 authenticateuser with the Authenticate?

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

### What are the rate limits for the Authenticate?

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 authenticateuser through Jentic?

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

### How many endpoints does the Authenticate have?

The Authenticate exposes 2 endpoints covering authenticate operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Authenticate operations the agent may call. This API works through OpenID operations rather than a resource id in the path, so you can allow only what the agent needs, such as starting an OpenID session with POST /authenticate/openid. The DELETE that ends a session is not available to the agent unless you add it.