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.