canonical: https://jentic.com/apis/aible.co.kr/aible # Aible Core API 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. ## For AI agents Create dementia diagnosis subjects, attach recordings, run AI analysis, stream queue status, and manage subject privacy, with coupon and session operations alongside. ## Scope Does not handle appointment scheduling, pharmacy, or EHR interchange. Use for managing dementia diagnosis subjects, recordings, and AI analysis results only. ## Capabilities - 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 ### 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. Example 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. Example prompt: 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. Example prompt: Generate an upload URL, register the recording for a diagnosis, then anonymize the subject by its subjectIdx once the screening is complete ## Key endpoints | 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 | ## Key resources - **Subjects** — Create, anonymize, and delete diagnosis subjects - **Diagnoses** — Create a diagnosis, mark AI analysis complete, stream queue status, and read single or completed diagnoses - **Records** — Generate an upload URL and register, list, and delete recordings for a diagnosis - **Coupons** — Reserve, register, approve, cancel, and search coupons for a member - **Auth** — Sign up, log in, refresh tokens, and exchange OAuth tokens for a session ## 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:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 62 / 100 - AI-Readiness & Agent Experience: 49 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 74 / 100 - **View full report:** https://jentic.com/apis/aible.co.kr/aible/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 ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Infermedica** — Infermedica runs symptom assessment and triage through a medical reasoning engine. - **DrChrono** — DrChrono manages electronic health records and clinical charting. - **athenahealth** — athenahealth provides EHR, patient records, and practice management. ## FAQ ### 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.