Sandbox Dbs Larciergroup DbSecure API
64
AI ReadinessAI-Aware (B)64/100
Community OpenAPI document · agent-readyIdentity AuthAuthenticationapiKey, basic3 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically generate access token, retrieve user data. Covers 3 operations with apiKey, basic authentication.
Use for: I need to generate access token, I want to user data, Search for revoke access token, List all records from DbSecure API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Larcier's identity provider methods. The API exposes 3 endpoints secured with apiKey, basic authentication.
Install Jentic One Beta
Connect the DbSecure API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DbSecure 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%2Fsandbox-dbs.larciergroup.com%2Fsandbox-dbs-larciergroup" | 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%2Fsandbox-dbs.larciergroup.com%2Fsandbox-dbs-larciergroup" | 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 DbSecure API.
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
Patterns agents use DbSecure API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — larcier's identity provider methods.
METHOD
PATH
DESCRIPTION
POST
/oauth2/token
Generate access token
POST
/oauth2/info
Retrieve user data
POST
/oauth2/revoke
Revoke access token
POST
/oauth2/token
Generate access token
POST
/oauth2/info
Retrieve user data
POST
/oauth2/revoke
Revoke access token
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.
D
DbSecure API
- AI-Aware (B)64/100
93
Foundational Compliance81
Developer Experience & Jentic Compatibility59
AI-Readiness & Agent Experience94
Agent Usability30
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
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.
81
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
50%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
59
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
87%
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.
30
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
30%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
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 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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DbSecure API through Jentic.
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.
GET STARTED