Tools and limits
What a credential can reach depends on its account type. The API enforces it. A sign-up at orinyx.io/developers creates a developer account.
What a developer account can call
| Tool | What it does |
|---|---|
start_a_test | Lists what your account can run and the next step for each. Start here. |
verify_order_text | Checks orders exactly as written, for example warfarin 5 mg by mouth daily. Orinyx splits each order into dose, route and frequency claims. |
verify_medications | Checks structured claims your agent already produces: {rawText, drug, claimType, structuredValue}. |
get_verification | Reads a saved run again, with its physician-review accuracy block if it has one. |
get_accuracy | The physician-review tally for one run. With no review yet, it says so and gives no numbers. |
export_verification | Exports a run as csv, pdf (full audit) or report (one-page PDF). The default is csv. |
Request limits
verify_order_text: up to 50 orders per request, 500 characters per order. One drug per order. An order that names two drugs, such asoxycodone/acetaminophen 5/325 mg by mouth every 6 hours, refuses the whole request.verify_medications: nine claim types:dose_range,route,frequency,indication,contraindication,interaction,monitoring,controlled_substance,rems_attestation. One claim type per claim, so an order with a dose and a route is two claims. Send one patient's medications per call.- Interactions: pass
check_interactions: trueon either tool to check the drugs in one request against each other, using the labels' own Drug Interactions text. - Optional:
tool_nameandtool_versionare named in the result header. - Run ids: the read-back tools need the full run id from the
Run id:line.
What is refused for a developer account
- Exams. Exams are for product accounts that Orinyx registers. A developer account calling
get_next_exam_case,get_exam_cases,submit_exam_answers,finish_examorget_exam_reportis refused. - Label and monograph lookups.
find_fda_label,read_fda_label_section,find_otc_monographs,get_otc_monographandread_otc_monograph_sectionare for staff accounts and are refused.start_a_testsays so under LOOK SOMETHING UP. Every flagged or supported row already carries its citation, with a link to the source. - The dashboard is for staff accounts. Signing in there with a developer account shows a page that points back to the connector.
How checks are counted
- The free plan is 200 checks per calendar month (UTC), one account per sign-up.
- One call to
verify_order_textorverify_medicationsis one check, however many orders it holds. - Lookups and read-backs do not count.
- Past the quota, checks are refused with
quota_exceededuntil the next UTC month.
Local, CLI and CI
The stdio server (python -m orinyx_mcp), the orinyx command-line tool and CI need an Orinyx API URL and an API key (ork_live_...) issued by Orinyx. A sign-up gives you the hosted connector only. The package is not on PyPI; install it from a checkout of the repository (Python 3.11+). orinyx verify and orinyx observe exit 0 clean, 2 flagged, 3 not verified and 1 on error, so a CI job can fail on a flag. The CI recipe is in the Quickstart on GitHub.
Source: GitHub v0.1.2
Version: v0.1.2, updated 2026-11-03