Aible Core API
68
AI ReadinessAI-Aware (B+)68/100
Community OpenAPI document · agent-readyHealthcareClinical Databearer41 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create dementia diagnosis subjects, attach recordings, run AI analysis, stream queue status, and manage subject privacy, with coupon and session operations alongside.
Use for: Create a diagnosis subject, Run AI analysis on a diagnosis, Check the status of a diagnosis queue, Upload a recording for a diagnosis
Not supported: Does not handle appointment scheduling, pharmacy, or EHR interchange. Use for managing dementia diagnosis subjects, recordings, and AI analysis results only.
The Aible Core API runs a dementia diagnosis workflow, creating diagnosis subjects, capturing recordings, and producing AI analysis results. A diagnosis is created against a subject, recordings are attached through a generated upload URL, and an analysis step marks the AI result as complete while a queue status stream reports progress. Subjects can be anonymized or deleted for privacy, and completed diagnoses are listed per member. The same platform also issues and redeems coupons and manages user sessions through signup, login, and OAuth.
Install Jentic One Beta
Connect the Aible Core API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aible Core 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%2Faible.co.kr%2Faible" | 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%2Faible.co.kr%2Faible" | 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 Aible Core API.
Create a diagnosis subject and attach records to it
Create a diagnosis and mark its AI analysis complete
Stream a diagnosis queue's status and list completed diagnoses for a member
Generate an upload URL and register recordings for a diagnosis
Anonymize or delete a diagnosis subject for privacy
Reserve, register, approve, and cancel coupons for a member
Authenticate users through signup, login, OAuth token exchange, and session refresh
Use Cases
Patterns agents use Aible Core API for, with concrete tasks.
★ Agent-Run Dementia Screening
An AI agent connecting through Jentic can drive a screening end to end: it creates a subject, requests an upload URL for the recording, registers the record, creates a diagnosis, and marks its AI analysis complete. Jentic injects the bearer token at call time, so the agent follows the clinical flow without ever holding the credential in its prompt.
Create a diagnosis subject, request a record upload URL, create a diagnosis for the subject, then mark its AI analysis complete
Diagnosis and AI Analysis
Produce and track an AI analysis result for a captured assessment. The Aible Core API creates a diagnosis against a subject, marks the analysis complete, streams the processing queue status so a caller can show progress, and reads a single diagnosis or the member's completed diagnoses back for review.
Create a diagnosis, subscribe to its queue status until processing finishes, then read the completed diagnosis by its diagnosisIdx
Recording Management and Subject Privacy
Capture recordings and keep subject data private. The Aible Core API issues a signed upload URL, registers the recording against a diagnosis, and lists a member's records, and it can anonymize or delete a subject so personal data is removed when a screening no longer needs to be identifiable.
Generate an upload URL, register the recording for a diagnosis, then anonymize the subject by its subjectIdx once the screening is complete
Key Endpoints
41 endpoints — the aible core api runs a dementia diagnosis workflow, creating diagnosis subjects, capturing recordings, and producing ai analysis results.
METHOD
PATH
DESCRIPTION
POST
/api/v1/subjects
Create a diagnosis subject
POST
/api/v1/diagnoses
Create a diagnosis
POST
/api/v1/diagnoses/{diagnosisIdx}/analyze
Mark AI analysis complete
GET
/api/v1/diagnoses/{diagnosisIdx}
Read a single diagnosis
POST
/api/v1/records/upload-url
Generate a record upload URL
POST
/api/v1/records
Register a recording
GET
/api/v1/diagnoses/me/completed
List completed diagnoses for a member
POST
/api/v1/subjects
Create a diagnosis subject
POST
/api/v1/diagnoses
Create a diagnosis
POST
/api/v1/diagnoses/{diagnosisIdx}/analyze
Mark AI analysis complete
GET
/api/v1/diagnoses/{diagnosisIdx}
Read a single diagnosis
POST
/api/v1/records/upload-url
Generate a record upload URL
POST
/api/v1/records
Register a recording
GET
/api/v1/diagnoses/me/completed
List completed diagnoses for a member
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.
A
Aible Core API
- AI-Aware (B+)68/100
87
Foundational Compliance62
Developer Experience & Jentic Compatibility49
AI-Readiness & Agent Experience94
Agent Usability75
Security74
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
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).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
23%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
49
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
53%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
93%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
51%
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.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
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 Aible Core API by hand means handling its bearer session tokens, the signup, login, OAuth, and refresh flow, and the generated upload URLs for recordings yourself. Through Jentic you install once, import Aible Core from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose which Aible operations your agent may call, so it can create and read diagnoses while deleting a subject or approving a coupon stays out unless you add them. Diagnosis and subject ids travel in the URL path (/api/v1/diagnoses/{diagnosisIdx}), so a rule can also pin the agent to one diagnosis.
Credential isolation
Your Aible token 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 'create a diagnosis' or 'run AI analysis', and Jentic returns the matching Aible 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 Aible Core API through Jentic.
What authentication does the Aible Core API use?
The Aible Core API authenticates with bearer tokens per its OpenAPI spec, with signup, login, OAuth token exchange, and refresh operations issuing and renewing the session token sent on protected calls. Through Jentic the token is injected at call time rather than living in the agent's prompt or logs.
Can I run an AI analysis on a diagnosis with the Aible Core API?
Yes. You create a diagnosis against a subject, mark its AI analysis complete, and subscribe to the diagnosis queue status stream to follow processing. The completed result is read back by the diagnosis's diagnosisIdx, and a member's completed diagnoses can be listed together.
What are the rate limits for the Aible Core API?
The OpenAPI spec does not specify rate limits. Check the Aible documentation at https://aible.co.kr for current limits before running a batch of diagnoses or recording uploads.
How do I create and analyze a diagnosis with the Aible Core API through Jentic?
Search Jentic for 'create a diagnosis' and it returns the diagnosis operations with their input schema. Your agent creates a subject, creates a diagnosis, attaches a recording through the upload URL, and marks the AI analysis complete. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Aible Core API?
Yes. Write a rule that allows only the diagnosis create and read operations, so the agent can run and read screenings while deleting a subject or approving a coupon stays out unless you add it, and every action it takes is logged. Because subject and diagnosis ids appear in the URL path, a rule can also pin the agent to one diagnosis.
Is there an Aible MCP server?
You don't need an MCP server to give your agent the Aible Core API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the subject, diagnosis, record, and coupon operations on demand without loading another server's tool definitions into its context.
GET STARTED