Your own agent, script or terminal can do what the Captain does for you: find events and register, read the codices, check your wallet, start a checkout. Same tools, three ways in.
A script, a cloud session or the CLI sends the key, and Pirate Skills treats the call as coming from you. It can read your wallet, access, profile and bookings, register you for a free event or cancel it, join Forge sessions, book an hour with Ben with one of your diamonds, and start a checkout link.
It never pays: a checkout is a Stripe link you open and complete yourself. It sees nobody else's data – no tool takes another person's id or email. It opens no admin tools. Each tool call costs one gold from your wallet, so you can see every call in your history.
PIRATESKILLS_API_KEY in your environment or secret store, never in code.Use a key under your own account. Organisation keys are refused.
Every door runs the same tools through the same checks. Pick the one your client speaks.
https://pirateskills.com/mcp
For Claude.ai, ChatGPT, Cursor and Claude Code. Sign in with your Pirate Skills account, or send your key as a header. Sign-in is required on this door.
https://pirateskills.com/api/public/agent/tools
For scripts, cloud sessions and anything that speaks HTTP. Public tools work without a key; your own data needs one.
pirateskills
A client on the HTTP API for your terminal: events, wallet, register, checkout, and any tool with run. Asks y/N before a change.
/mcp/admin
For the Pirate Skills team only. An ordinary key or sign-in gets a not-found, and big changes still wait for a click on our admin page. Nothing on this page opens it.
Settings → Connectors → Add custom connector, paste the URL, then sign in with your Pirate Skills account.
https://pirateskills.com/mcpSettings → Apps & Connectors → Advanced settings → turn on developer mode → Create, paste the URL, sign in.
https://pirateskills.com/mcpAdd the server, then run /mcp to sign in – or send your key as a header for a headless or cloud session.
claude mcp add --transport http pirateskills https://pirateskills.com/mcp
claude mcp add --transport http pirateskills https://pirateskills.com/mcp \
--header "Authorization: Bearer $PIRATESKILLS_API_KEY"Add this to .cursor/mcp.json. Leave out headers to sign in in the browser instead.
{
"mcpServers": {
"pirateskills": {
"url": "https://pirateskills.com/mcp",
"headers": { "Authorization": "Bearer ${env:PIRATESKILLS_API_KEY}" }
}
}
}Install the skill: when to use which tool, and the rules for asking before a change.
npx skills add https://pirateskills.com/skills/pirateskills/SKILL.mdGET the base URL to list the tools open to you. POST a tool's input as JSON to run it. Send your key as a bearer token.
A visitor sees the public tools. Listing is free and never costs gold.
curl https://pirateskills.com/api/public/agent/toolsReads also work as a GET with the input in the query string, handy in a browser.
curl -X POST https://pirateskills.com/api/public/agent/tools/list_events \
-H "content-type: application/json" \
-d '{"limit": 3}'
curl "https://pirateskills.com/api/public/agent/tools/search_knowledge?query=landing%20page&limit=2"Put the key in an environment variable, never in code. One gold per call.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_wallet \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{"limit": 5}'Writes run on POST only. An agent asks the person first, every time.
curl -X POST https://pirateskills.com/api/public/agent/tools/register_for_event \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-H "x-agent-client: my-script" \
-d '{"eventId": "2026_09_23_ai_compass"}'Always JSON with ok. The listing also says who you are and, per tool, confirm (it changes something) and its inputSchema as JSON Schema. The optional x-agent-client header names your client in your wallet history.
{ "ok": true, "tool": "list_events", "result": [ … ] }
{ "ok": false, "error": "Sign in to use my_wallet." }No dependencies, Node 18 or newer. Not on the npm registry yet – install it straight from pirateskills.com.
login checks the key and saves it, readable only by you, in your OS config folder. PIRATESKILLS_API_KEY in the environment wins, so cloud sessions skip login.
npm install -g --allow-remote=all https://pirateskills.com/cli/pirateskills.tgz
pirateskills login # paste your key, or set PIRATESKILLS_API_KEY
pirateskills toolsOr run a command once, without installing. --allow-remote=all lets npm 12 and newer install from a URL; older npm ignores it.
npx -y --allow-remote=all https://pirateskills.com/cli/pirateskills.tgz events --limit 3A command that changes something shows what it will do and asks y/N. --yes skips the question for a script; without a terminal and without --yes, nothing runs.
pirateskills events --limit 5
pirateskills search "landing page"
pirateskills wallet
pirateskills register 2026_09_23_ai_compass # asks y/N first
pirateskills checkout pirate_pass # a Stripe link, never a charge
pirateskills checkout captain_on_deck_session --quantity 3 # three sessions, one link
pirateskills checkout forge_pass --currency usd # charged in dollars (default: your country)
pirateskills run my_bookings --json '{"timeZone": "Europe/Berlin"}'Gold comes with a pass each month and from showing up to events. Your wallet shows every call an agent made.
register_for_event, cancel_registration, create_checkout, join_forge_cohort, book_hour_with_ben. Call one only when the person asked for it, say what will happen, and wait for their explicit yes – every time.All 14 tools on the MCP door and the HTTP API, generated from the same list the doors are built from.
Search the Pirate Skills knowledge: the Growth Codex, the Builder Codex and Captain's Insights. Returns the best matching chapters with a short excerpt and a link. Cite the url of every chapter you use in your answer.
curl -X POST https://pirateskills.com/api/public/agent/tools/search_knowledge \
-H "content-type: application/json" \
-d '{ "query": "<query>" }'Upcoming Pirate Skills events (Pirate Lab, AI Compass, Vibe Coding Cologne, the Vibe Hackathon, Forge sessions), soonest first, with a link to each event page (a Forge session links the Forge page, where the seat is sold) and, for a signed-in person, whether they are registered.
curl -X POST https://pirateskills.com/api/public/agent/tools/list_events \
-H "content-type: application/json" \
-d '{}'What Pirate Skills sells right now, with prices, read live (only what is on sale appears, and only what create_checkout sells): the Pirate Pass and the Forge Pass (monthly, prices before VAT, three-month minimum), which replace the Pirate Forge tiers (those are listed only until the passes are on sale), and a Captain on Deck session with Ben (the price is per session; up to 10 in one checkout) while it is on sale – each bought with create_checkout. `priceText` is the price to quote: euros, plus US dollars once a dollar price is set (both in one string, "€ / $"), with the person's likely currency first. An offer marked purchasable false carries a note saying why (a Pirate Pass holder cannot buy the Forge Pass on top). Event tickets (the Vibe Hackathon) are not listed here: a ticket is bought on the event page from list_events, where the price depends on the date and tier. Free events are registered with register_for_event, and the free Codex is read with search_knowledge. Every purchase is paid by the person on Stripe's own page; no agent takes a card or charges anyone.
No inputs.
curl -X POST https://pirateskills.com/api/public/agent/tools/get_offers \
-H "content-type: application/json" \
-d '{}'Register the signed-in person for a free upcoming event by its id (from list_events). Paid events are not registered here: the answer carries the event page where a ticket is bought.
curl -X POST https://pirateskills.com/api/public/agent/tools/register_for_event \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{ "eventId": "<eventId>" }'Cancel the signed-in person's own registration for an event by its id.
curl -X POST https://pirateskills.com/api/public/agent/tools/cancel_registration \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{ "eventId": "<eventId>" }'What the signed-in person has access to on Pirate Skills: the Codex, event series, the Forge, tools — with when and how each was unlocked.
No inputs.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_access \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'Start a purchase for the signed-in person and get back a Stripe checkout link, for an offer key from get_offers: the Pirate Pass or the Forge Pass, Captain on Deck sessions while they are on sale, or a Pirate Forge tier while one is still listed. `quantity` (1–10, default 1) is only for Captain on Deck sessions (`captain_on_deck_session`): one checkout buys that many sessions, one diamond each; any other offer with a quantity is refused. `currency` (`eur` or `usd`) is what Stripe charges in; leave it out and the checkout follows the caller's country when the request carries one – euros in Europe, dollars elsewhere – else euros. An offer without a dollar price is charged in euros either way. Event tickets are not sold here: send the person to the event page from list_events. Give the person the link; they pay on Stripe's page themselves. No agent ever charges a card, and nothing is charged until the person completes that page. The sale is credited to the agent that started it.
curl -X POST https://pirateskills.com/api/public/agent/tools/create_checkout \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{ "offerKey": "<offerKey>" }'The signed-in person's wallet: `gold.balance` and `diamonds` are counts; `emerald` is the pass they hold, in words ("Pirate Pass until 17 Oct 2026", "Forge Pass until …" or "no pass") – emerald is never a number, so never give it as one. Also how much of this month's gold drip is left and what they earned, the next refill date, when earned gold expires next (earned gold keeps twelve months, oldest first; `gold.expiresNext` is the amount and day within 60 days, or null), and the recent history. What gold is and buys, for the person: https://pirateskills.com/gold.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_wallet \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'The signed-in person's referral link, the people who signed up through it (first name and initial), and what each brought: gold or a diamond already paid, rewards pending with their pay date, and rewards not paid with the reason. Referrals pay nothing on signup; they pay when someone brought shows up to their first event, buys, or joins the Forge, after a wait and not at all if the purchase is refunded in that time. What each outcome pays right now and the wait in days are in `terms`, read from the live rules; `terms.on` false means rewards are paused.
No inputs.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_referrals \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'The signed-in person's name and email as Pirate Skills knows them.
No inputs.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_profile \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'The Pirate Forge live sessions the signed-in person can still join: each upcoming quarter's Build phase (weeks 1–6) and Grow phase (weeks 7–12), sessions left, and whether they are in. Empty with hasAccess false when they hold no active Forge access.
No inputs.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_forge_sessions \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'Join the signed-in person to Pirate Forge live sessions: a whole cohort from now on (phase "all") or one phase ("build" or "grow"), by quarter key from my_forge_sessions. Only sessions still ahead are added; needs active Forge access. The answer says whether the calendar invite went out or Ben adds it by hand.
curl -X POST https://pirateskills.com/api/public/agent/tools/join_forge_cohort \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{ "quarterKey": "<quarterKey>", "phase": "build" }'The signed-in person's hours with Ben: how many diamonds they hold (one diamond = one hour, one to one), their bookings with status (held, confirmed, cancelled) and join link, and the open hours in the next three weeks they can book with book_hour_with_ben. Pass their time zone to get the open hours in it.
curl -X POST https://pirateskills.com/api/public/agent/tools/my_bookings \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{}'Spend one of the signed-in person's diamonds on a one-to-one hour with Ben, at an open hour from my_bookings (pass its start exactly as listed). The diamond is held at once and spent when Ben's calendar confirms, usually within a minute; if the hour is not booked it comes back. The person can cancel on the booking page before the hour starts and get the diamond back.
curl -X POST https://pirateskills.com/api/public/agent/tools/book_hour_with_ben \
-H "Authorization: Bearer $PIRATESKILLS_API_KEY" \
-H "content-type: application/json" \
-d '{ "start": "<start>" }'