DEVELOPER DOOR

Every call is a POST to the API base with two credentials. The project key identifies the project and travels in the apikey header. It is public, and it is not your credential:

API base    https://igeyvnwkivwcexrpftsp.supabase.co
Project key sb_publishable_Nv060ZycyVLkoJ-HCsyVpQ_qXg4D9MO

Your credential is a partner API key, sent in the JSON body of every call as p_api_key. A key looks like this: kx_live_ followed by 32 characters. Keys are issued by the KINEX team, by hand. There is no self-serve signup and no key vending. To request a key, email info@stitchverse.net with your company and what you are building. A key is shown once, at issue. KINEX stores only its SHA-256 hash, never the key itself, and a key can be revoked at any time. Treat your key as a secret: a call made with it is recorded against your integration.

Errors are plain. A missing, malformed, or revoked key returns 401 with the message “invalid or missing API key”. A call that names something the catalog does not hold returns 400 with the reason, for example “work not found”. Error bodies carry the platform’s code, message, details, and hint fields; the message is the part written for you.

READ THE CATALOG

POST/rest/v1/rpc/kinex_api_get_catalog

Returns every work in the catalog of record, in catalog order. Each work carries its id, title, form, choreography credit where the record states one (unstated credits are returned empty, never inferred), performers, seal, gate status, a plain note on the status, and the work’s Record Room address. What a work carries beyond this, chain-of-title internals, consent documents, fixation data, is not served here at any key level.

curl -X POST \
  https://igeyvnwkivwcexrpftsp.supabase.co/rest/v1/rpc/kinex_api_get_catalog \
  -H "apikey: sb_publishable_Nv060ZycyVLkoJ-HCsyVpQ_qXg4D9MO" \
  -H "Content-Type: application/json" \
  -d '{"p_api_key": "kx_live_YOUR_KEY"}'

// 200, excerpt
[
  {
    "id": "encore",
    "title": "Encore",
    "form": "Duet",
    "choreography": "Blacka Di Danca & Seiky Stephanie",
    "performers": "Blacka Di Danca, Seiky Stephanie",
    "seal": "DKA Certified",
    "gate_status": "pass",
    "gate_note": "Passed the full-piece fm-rev5 gate.",
    "record_url": "https://kinex.stitchverse.net/record-room.html"
  },
  {
    "id": "nymm",
    "title": "NYMM",
    "form": "Five-dancer work",
    "choreography": "Seiky Stephanie",
    "performers": "Five dancers",
    "seal": "DKA Certified",
    "gate_status": "pass",
    "gate_note": "Passed the fm-rev5 gate on the ruled span of record.",
    "record_url": "https://kinex.stitchverse.net/record-room.html"
  }
]

Gate status is stated exactly as the record holds it. A work cataloged by founder acceptance says so in its note, with the gate’s reading named. It is never rounded up to a pass.

READ ONE WORK

POST/rest/v1/rpc/kinex_api_get_work

The same record for one work, named by its catalog id in p_work_id. An id the catalog does not hold returns 400, “work not found”.

curl -X POST \
  https://igeyvnwkivwcexrpftsp.supabase.co/rest/v1/rpc/kinex_api_get_work \
  -H "apikey: sb_publishable_Nv060ZycyVLkoJ-HCsyVpQ_qXg4D9MO" \
  -H "Content-Type: application/json" \
  -d '{"p_api_key": "kx_live_YOUR_KEY", "p_work_id": "encore"}'

// 200
{
  "id": "encore",
  "title": "Encore",
  "form": "Duet",
  "choreography": "Blacka Di Danca & Seiky Stephanie",
  "performers": "Blacka Di Danca, Seiky Stephanie",
  "seal": "DKA Certified",
  "gate_status": "pass",
  "gate_note": "Passed the full-piece fm-rev5 gate.",
  "record_url": "https://kinex.stitchverse.net/record-room.html"
}

REQUEST A LICENSE

POST/rest/v1/rpc/kinex_api_request_license

Files a structured license request against one work, or against the catalog as a whole. The request is recorded with a reference, the team is notified at once, and the team replies to your contact email. A request is an expression of interest. It issues no license, quotes no price, and takes no payment.

p_api_key

Required. Your partner API key.

p_work_id

A catalog work id, or null for a catalog-wide request. An unknown id returns 400.

p_company

Your company or organization.

p_contact_name

The person the team should answer.

p_contact_email

Required. A valid email. The team’s reply goes here.

p_use_case

What the movement is for, in your words: a game, a film, a world, a dataset.

p_notes

Anything else the team should know.

curl -X POST \
  https://igeyvnwkivwcexrpftsp.supabase.co/rest/v1/rpc/kinex_api_request_license \
  -H "apikey: sb_publishable_Nv060ZycyVLkoJ-HCsyVpQ_qXg4D9MO" \
  -H "Content-Type: application/json" \
  -d '{
    "p_api_key": "kx_live_YOUR_KEY",
    "p_work_id": "encore",
    "p_company": "Your Company",
    "p_contact_name": "Your Name",
    "p_contact_email": "you@yourcompany.com",
    "p_use_case": "Game integration evaluation",
    "p_notes": ""
  }'

// 200
{
  "id": "a recorded request id (uuid)",
  "ref": "KX-LR-114040",
  "status": "received",
  "licensing_opens": "2027",
  "note": "A license request is an expression of interest. The KINEX team replies by email; a request issues no license, and licensing opens in 2027."
}

1. Your call lands as a recorded request with a reference, KX-LR followed by six characters. Keep the reference; the team will use it.
2. The team is notified at once and replies to your contact email. Terms are discussed there, bilaterally, the way every KINEX license is made.
3. When the team acts, the request is promoted into the transaction layer as a tracked license record for the licensor of record, DANCA Media LLC, and advances from status “requested” under the team’s hand.
4. Licensing opens in 2027. Until then a request holds your place in the conversation. It is not a license, a quote, an option, or a reservation of rights.

Licensed movement is delivered as The Bundle: the character and its movement as GLB and FBX files, the full cast and each dancer on their own, with the record’s formation, a consent summary, and the record’s verification inside. The Bundle is build two of the KINEX build order. It is built, and the catalog’s records are packaged in The Studio today. Delivery of a package rides on an executed license; nothing on this page offers a file.

The delivery contract is specified now so a partner can build against its shape: delivery rides on an executed license, never on an API key alone. The Bundle is built and its records are packaged in The Studio; the API-side manifest endpoint is not built, and until it is, the read endpoints above are the whole of what the API serves. Any tool that claims to pull KINEX assets through this API today is describing something that does not exist.