How a pilot runs, what the reviewer does, and what integrators can call.

How a pilot runs

One queue. The practice sends a denial and a chart excerpt; we prepare the packet; the practice's reviewer approves it, approves it with a correction, or rejects it; the decision goes on a sealed record; the month is invoiced from that record. The $499 design writes the queue, the owner, the approval gate, the exception path, the baseline and the scorecard down before the first packet. The flagship template shows the steps; the worked example shows a real record on made-up denials.

For the reviewer

• Your console is the link in the email you received with your free packet, your packet purchase or your pilot. The link carries your reviewer key; we do not keep a copy. If it is lost, enter your email at your console page and we send a fresh link; the old one stops working.
• Your account. Create an account with the email you bought with and confirm it once; your account then lists every console and packet request for that email and opens each console without the emailed link.
• Three decisions: approve as is; approve with a correction, where you write the rule the next packet must follow; or reject, which is recorded and never charged.
• Corrections bind. Every packet prepared after your correction cites it, and the console shows the rules in force at the top and on each pending item.
• The record. Every decision is one event in a chain sealed with a published key. The console shows the seal and the one command that verifies your export from any machine.
• This month. The console shows completed items against the bundle and the count per item that the invoice will use. The month closes on the 1st.

For the practice administrator

• Sending work. For the free packet, one de-identified denial through the form. For paid packets, one de-identified denial per packet, from the link in your purchase email or from your console, which counts how many you have left. During a managed pilot, denials and chart excerpts come through the upload in your console, under the signed Business Associate Agreement. Email carries notifications and links only and never carries patient data.
• Turnaround. Free and paid packets are in your console within two working days of the denial arriving; pilot turnaround is set in the design and measured on the record.
• What counts. A completed item is a packet a reviewer approved, with or without a correction. Rejected packets are recorded and never charged. 400 completed items a month are included at $2,500; $6 each after.
• Invoices. Computed from the sealed rows, previewed per item in the console, sent through Stripe after the month closes.
• Data. How it moves, who processes it, what we hold and for how long: the security page. Terms are on the terms page.

For integrators

Everything the console does is an HTTP call. Public, no key: GET /v1/ledger/public-key returns the Ed25519 public key and its id; POST /v1/ledger/verify takes a ledger export ({events, seal}) and answers {ok, checks: {chain, head, signature, count}, detail}, 422 when anything fails; GET /example/ledger.json is a public export to try it on. With a reviewer key (as Authorization: Bearer or ?key=): GET /v1/pilots/{id}/ledger exports the pilot; POST /v1/pilots/{id}/items/{item}/decision with {decision, note, correction, reviewer} records a decision; GET /v1/pilots/{id}/invoices/{YYYY-MM|current|previous} previews a period. To request a free packet by API: POST /v1/sample with {name, email, practice, role, denial, noPhi: true}. Operator calls (creating pilots and items, closing months) are ours; a partner who wants them gets a token under a written agreement.

Verify a record yourself

curl -s 'https://appeals.strategic-innovations.ai/example/ledger.json' \
  | curl -s -X POST -H 'content-type: application/json' --data-binary @- https://appeals.strategic-innovations.ai/v1/ledger/verify

Change one character of the export and the same command answers "ok": false with the reason.