A worked G-to-F example for a hypothetical service-key request. We read the complete piano PDF in our development account, using four existing reading credits. No new credits were purchased.
The source is Pianocoda’s Amazing Grace arrangement. Two bass notes in printed bars 3 and 7 needed correction from B2 to C3 before transposition. Every checked note was compared against the original page.
The actual request asked to move the whole part from G to F, preserving rhythm, ties, triplets, phrasing, dynamics and accompaniment, without simplification or reharmonization. Every note in the AI result moved exactly two semitones lower. We removed two unsupported title/tempo text lines and used the normal title control before the final save.
Both scores contain the same 96 quarter-note beats, including a one-beat pickup and final two-beat measure. Each PDF has two pages. All 198 written notes and their durations match MusicXML; the 194 performed MIDI notes match playback. Four tie connections and four triplet groups are retained. Tempo is a steady 72 BPM.
The PDFs, MIDI and MusicXML were downloaded through the product after a development export improvement added explicit MusicXML tie ends. These export changes are a development preview, not yet a production release.
Source pedal markings are omitted; some expression and layout differ. This is checked notation, not a facsimile. The piano playback does not follow a singer, supply a vocal part or model service rubato. The scenario does not describe a real customer or imply a church endorsement.
Changing the key of an already-read score is free. Recurring services alone do not establish recurring paid reading; new piano PDF/photo intake is what uses reading credits.