canonical: https://jentic.com/apis/sandbox-dbs.larciergroup.com/sandbox-dbs-larciergroup

# Sandbox Dbs Larciergroup DbSecure API

Larcier's identity provider methods. The API exposes 3 endpoints secured with apiKey, basic authentication.

## For AI agents

Programmatically generate access token, retrieve user data. Covers 3 operations with apiKey, basic authentication.

## Scope

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

## Capabilities

- Generate access token
- Retrieve user data
- Revoke access token
- Query and filter DbSecure API records by parameters
- Monitor DbSecure API operational status and events

## Use cases

### Identity and Authentication Operations

Use the DbSecure API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including generate access token, retrieve user data, revoke access token.

Example prompt: Call POST `/oauth2/token` to generate access token

### Automated OAuth2 Management

Automate oauth2 operations by combining multiple DbSecure API endpoints. Agents can retrieve user data and then revoke access token in a single workflow.

Example prompt: Call POST `/oauth2/info` to retrieve user data, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth2/token` | Generate access token |
| POST | `/oauth2/info` | Retrieve user data |
| POST | `/oauth2/revoke` | Revoke access token |

## Key resources

- **OAuth2** — OAuth2 methods

## 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: 93 / 100
  - Developer Experience & Jentic Compatibility: 81 / 100
  - AI-Readiness & Agent Experience: 59 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/sandbox-dbs.larciergroup.com/sandbox-dbs-larciergroup/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 the DbSecure API by hand means handling its basic-auth client credentials to mint a bearer token, sending that Authorization header to the sandbox host, and managing token revocation and retries yourself. Through Jentic you install once, import DbSecure from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** DbSecure sends its OAuth targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as generating or introspecting a token. You choose that allowed set, so revoking tokens is not included unless you add it.
- **Credential handling:** Your DbSecure client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate an access token' or 'get token info', and Jentic returns the matching DbSecure 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 DbSecure API use?

The DbSecure API uses apiKey, basic 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 generate access token with the DbSecure API?

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

### What are the rate limits for the DbSecure 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 generate access token through Jentic?

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

### How many endpoints does the DbSecure API have?

The DbSecure API exposes 3 endpoints covering oauth2 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which DbSecure operations the agent may call and which credentials it may use. You can allow only what the agent needs, such as generating a token with POST `/oauth2/token` or introspecting one with POST `/oauth2/info`, and leave POST `/oauth2/revoke` out of the allowed set unless you add it. Since DbSecure passes its OAuth targets in the request body rather than the URL, this operation-level allow list is what governs what the agent can do.