Quickstart

Not for clinical use. Orinyx checks medication claims against cited FDA label text for testing and evaluation only. Do not use its results to diagnose, treat, prescribe or make patient care decisions. Use synthetic test data only.

This uses the hosted connector. There is nothing to install. The free plan includes 200 checks per calendar month (UTC).

First run

1. Sign up at orinyx.io/developers.
2. Open the welcome email and click Set your password. The link can be used once.

3. Connect Claude Code. Run:

   claude mcp add --transport http orinyx https://orinyx-mcp.fly.dev/mcp

   Then run /mcp inside Claude Code and authenticate. You are sent to the Orinyx sign-in page. Sign in with your email and the password you set. More on the Claude Code page.

4. Type "start a test". The agent calls start_a_test, which lists what your account can run. The examples below use the quick check, verify_order_text.

5. Run the clean example. Ask:

   Check this order with verify_order_text, exactly as written: warfarin 5 mg by mouth daily.

6. Run the planted example. Ask:

   Check this order with verify_order_text, exactly as written: acetaminophen 1500 mg by mouth every 4 hours.

7. Compare each result with the expected results below.

Both orders are also in the repository under examples/first-run/ (clean.txt, planted.txt).

Expected results

The expected results were captured on 2026-10-22 from Orinyx engine 0.3.1 on a local machine, through this package's MCP server. Your run should have the same rows, the same verdict and severity on each row, and the same citations. The run id, the "Orinyx checking time" line and the header will differ. Your agent may summarize the result in its own words. To compare line by line, ask it to show the tool's output exactly as returned.

Clean example: warfarin 5 mg by mouth daily

Three claims, all supported, no flag.

All three rows cite one label: SPL set ID 5a5b5e3a-6556-a542-e063-6294a90a6d3f, with a DailyMed link. The dose row says no 24-hour maximum is on file for warfarin, so the daily total was not checked. The run ends with: "This is not a safety clearance; claims not verified were not checked."

Planted example: acetaminophen 1500 mg by mouth every 4 hours

One flag, two supported. The error is planted so you can see a flag. It is not a dosing example.

The dose row reads "every 4 hours" as 6 doses in 24 hours: 1,500 mg × 6 = 9,000 mg. The cited monograph paragraph states a maximum of 4,000 mg in 24 hours. The severity comes from Orinyx's curated rule for that dose limit. The route and frequency rows cite SPL set ID 7f445de3-30cf-4bd8-892d-05979cd399e7. That label is for children, not for the adult order written here; this is limit REG-012 on Known limits.

If you get a different verdict for either order, the API you reached holds different reference data from the engine that produced these results. The verdict the API returned is the one to read.

Limits

• Synthetic data only. Never send real patient records, names, dates or record numbers.
• Supported is not a clearance. A supported row means one claim agrees with the cited label text. It is not a judgment that the order suits a patient. It does not clear the daily total, the schedule or the patient context unless a row says so.
• Not verified means unchecked. A not verified (abstained) row was not checked. It does not mean the claim is correct.
• Orinyx flags; the clinician decides. No language model decides a verdict or a severity.

Read Known limits before you rely on a result.