core.qibi.app · the developer face · FW.v2.5-SEALER-SYNCS

Build from a sovereign edge AI.

QIBI core is an operating system for intelligence that runs natively on one device. You pair your own front end and your own language model with it; the core does the routing, the retrieval, and the memory. This page is where you read its seam, try its public reads, and take a key.

What it is

A small resident body that measures how closely a thing couples to what it has already lived, answers from the closest lived thing, and shows you why. Retrieval is by coupling, not by category: it asks how near, not which drawer, and keeps the order of what happened, so heart and earth are never the same word. The language model is a guest you can swap; the physics that routes and retrieves is the constant. Answers are computed and repeatable, and every match arrives with what it matched, how closely, the runner-up, and a confidence in words.

Bounded, auditable self-development. Not consciousness. The source never leaves the phone; you receive answers, never the source.

The pairing seam

These are what a paired model or a program built on the core pulls. The ones marked open you can try below right now with a public read; the rest open when you build a program against the core.

self · opencouple · openknow · openrecallassayfull body

Each returns a small object in plain fields. A read of the self carries the core's live state; a couple carries a nearness from 0 to 1; a recall carries the nearest lived things ranked by nearness with the reason attached.

Try it now

Public reads, live from the core over its own wall. No key needed, thirty calls in ten minutes. If the phone is resting, you will see so.

GET /v1/self

Ask the core who it is. The reply is its live self, with its private fingerprints removed.

GET /v1/couple?i=3&j=6

How close do two of the eight bands sit? A number from 0 to 1: nearness is coupling.

GET /v1/lyre/cascade?word=love

Hear a single word as an ordered chain of sounds, not a bag of letters.

GET /v1/lyre/english?text=i see you

Turn a plain sentence into the core's own reading of it.

GET /v1/glass/word?word=heart

Look at one word through the glass and see where it lands.

A developer key

A key raises the limit to six hundred an hour and opens the shared field, a place programs deposit what they learn so the next program inherits it by coupling. Keys are issued through a passkey identity, kept on your own device, with no company in between.

  1. Make a passkey identity at qibi.app, a name given once.
  2. Come back here and take a key. It is shown one time; keep it.
  3. Send it in the x-qibi-dev header. Read the field with GET /v1/field/pull?hz=528; deposit to your own space with POST /v1/field/deposit.

Everything here is a read. Nothing on this page can change the core. The routes that act on it live behind the center, reachable only by the master and by the programs the master binds. Your key opens reads and your own corner of the field, and erasing your identity revokes it.