Documentation

Getting started

Kakehashi speaks the OpenAI API. If your code already calls an OpenAI-compatible endpoint, the integration is a base URL and a key — and this page walks the whole way there, from the invitation email to your first answer.

1. Getting access

Kakehashi is invite-only. There is no self-service sign-up form: an operator invites your email address, and only an invited address can sign in or hold a key. If you have not been invited yet, write to kakehashi@classmethod.my.

If your company already uses Kakehashi you do not need us at all — an administrator in your own organization can invite you from their portal. See Organizations and groups.

Open the portal and enter the address that was invited. Three ways in are offered, and they all end in the same place:

Email link — we email you a one-time sign-in link. Nothing to remember, nothing to leak.
Email and password — create a password the first time. You will be asked to verify the address by email before the account works.
Continue with Google — if your work email is a Google account.

Your email address has to be verified

Every call the portal makes checks that your address is verified and still invited. An unverified address is refused, and signing in again re-sends the verification email.

3. Choosing an account type

The first time you sign in you are asked one question: whether Kakehashi is just for you, or for a team.

Just for me — you issue and manage your own keys, and your credit is yours alone.
Set up an organization — you become the organization's first admin. Credit is shared with everyone you invite, and spending can be split into groups with their own limits.

You also pick a billing country — Malaysia, Thailand or Singapore. It decides the currency you are charged in and the tax that applies, so it is worth getting right.

Both choices are made once

Neither the account type nor the billing country can be changed later from the portal. Contact support if you picked the wrong one.

4. Issuing an API key

Keys live on the portal's API Keys page. Give a key a label you will recognise later, and optionally a budget cap; leaving the cap empty means the key may spend the whole balance it draws on.

The key is shown exactly once

The full key value appears in a dialog immediately after it is created, and never again — not on that page, not from support. Copy it into your secret store before closing the dialog. If you lose it, revoke the key and issue a new one.

If you are a plain member of an organization you will not see a form to issue a key. An admin grants one to you instead, and a Keys waiting for you card appears on your dashboard with a Collect key button. The key is created at the moment you collect it, so not even the admin who granted it ever sees the value.

5. Your first request

Point your existing OpenAI client at the Kakehashi base URL and pass your key as a bearer token. The model name in the request body decides which model answers.

curl https://api.kakehashi.classmethod.my/v1/chat/completions \
  -H "Authorization: Bearer $KAKEHASHI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "<model-id>", "messages": [{"role": "user", "content": "Hello"}]}'

Replace $KAKEHASHI_API_KEY with the key you just copied, and <model-id> with a model id from the catalogue. Once you are signed in, the portal's Models page shows these same snippets with the model you picked already filled in.

Which base URL to use

The base URL for this environment is https://api.kakehashi.classmethod.my. The OpenAI SDKs want it with /v1 appended; the Claude Code CLI wants it without. The snippets above already do the right thing for each.

6. Adding credit

A new account has no balance, and requests are refused once the balance is used up. Add credit from the portal's Top up page: you buy a fixed amount of US-dollar credit and pay in your own currency at that day's exchange rate.

In an organization only an organization admin can top up; everyone else spends the shared balance. The full rules are in Billing and credit.

Where to go next

Set a warning threshold, so you hear about a shrinking balance before it stops your traffic — Notifications.
Learn what each status code means before you meet one in production — Errors and limits.
Invite your colleagues and split the budget — Organizations and groups.