Guitar capo key calculator
This guitar capo key calculator turns the chord shapes you finger with a capo into the actual concert pitches listeners hear.
Run — free
Place a capo on a fret, play open-position shapes such as G, Em, C, and D, and the sounding chords rise by that many frets in twelve-tone equal temperament while every quality suffix stays intact. Songwriters, teachers, and cover bands use the mapping constantly: a song written in G shapes with capo two sounds in A; the same shapes with capo five sound in C. The engine is fully deterministic arithmetic on pitch classes modulo twelve, with no network calls, no sampling, and no date-dependent shortcuts. Capo zero is a valid identity that leaves chords unchanged; a negative fret is rejected as invalid input. Use it free in the browser when arranging charts, checking a lead sheet, or teaching how capos work, or call the API at $0.002 per successful request when you need reproducible sounding keys and chord lists in CI, set-list tools, or tutoring software.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/hobby/capo-key \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"capo":2,"chords":["G","Em","C","D"]}'const res = await fetch("https://api.kit.forhosting.com/hobby/capo-key", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"capo": 2,
"chords": [
"G",
"Em",
"C",
"D"
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/hobby/capo-key",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"capo": 2,
"chords": [
"G",
"Em",
"C",
"D"
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/hobby/capo-key", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"capo":2,"chords":["G","Em","C","D"]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"capo":2,"chords":["G","Em","C","D"]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/hobby/capo-key", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"capo": 2,
"chords": [
"G",
"Em",
"C",
"D"
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "hobby.capo_key",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_capo | 24 |
max_chords | 64 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |