Connect: three stages, try first, sign later

This page answers three questions only: how to start, what you can get today, who to write to.

1. Three stages

Stage	What can happen	What gets signed	How to exit
① Introduction and authorisation	Agree the scope: which countries, which kind of capacity, how compute is counted, who answers to the regulator.	A confidentiality agreement; a letter of intent (scope, term, and whether it is exclusive).	The letter of intent lapses at the end of its term; either side may end it in writing, and material already exchanged is handled under the confidentiality agreement.
② Test environment	Run the link with sample capacity and sample operating entities, and leave with a result you can recompute yourself. The present state is in section 2, stated as it is.	Covered by the confidentiality agreement; no separate commercial contract.	Leave at any time; the test environment holds no real capacity, no real licence and no real user data.
③ Live connection	The same way of connecting: swap the address and the credentials for the live ones and you are running; commercial terms, service levels and the settlement cycle are fixed in this stage.	A technical services contract; data-processing terms (data plane deployed locally, data does not leave the country).	Per the exit clause: disposal of data and assets, hand-over support and transition support, each written out.

One design statement: once the test environment is built it will use the same API endpoints as production — API endpoints being the HTTP addresses a partner's system calls. What runs with us runs in production. That is a design commitment, not a claim that a test environment exists today; the present state is in the next section.

2. The test environment as it stands (stated as it is)

The test environment is under construction. What is available today: three offline test vectors + recomputation notes + one self-test script (runs offline, standard library only, counts usage but not money), plus integration notes for the three open endpoints.

What does not exist yet, listed one by one (not reworded): no test environment entry address, no self-service credential entry, no online application page, and no isolated environment that is identical to production. When the test environment is built, this box will be replaced by an entry address and credential instructions; until then, this box is this paragraph.

3. How to connect (the short version)

Three write endpoints (all require a Bearer credential):

Endpoint	Path	Request fields	What comes back
Device registration	`POST /v1/devices`	4 fields: certificate request, device fingerprint, protocol version, capability set	Activation state, certificate reference, protocol version, response headers
Device heartbeat	`POST /v1/devices/{id}/heartbeat`	3 fields: heartbeat interval, network quality, configuration negotiation	Negotiated interval, server time, whether the configuration was accepted
Usage reporting	`POST /v1/billing/events`	9 fields: ledger item number, tenant, device, user, service type, quantity, amount, currency, time of occurrence	Whether it was posted, and which ledger item it hit

Three request headers: trace number (32 hexadecimal characters), protocol version (of the form 1.0), idempotency key (optional, recommended for writes). What the idempotency key does, in one line: the same key submitted again does not add an entry to the ledger; the same key with different content is refused.

4. Document slots (supplied on request, not hosted on this site)

This site does not host copies of these files — hosting means maintaining, and maintenance that stops becomes dead links. So only the names and purposes are listed; write for the originals (address in section 7).

Field definitions for the three write endpoints: what goes in each field, what type, required or optional, plus one complete example each.
The blank form for a compute-usage request (8 fields): exchange number, dimension, metering item, unit, quantity, start, end, reconciliation granularity. The quantity field is a decimal-integer string; sent as a number it is refused — that is the hard discipline for amounts and quantities.
Cross-dimension conversion register: 6 communications units × 5 compute units = 30 pairs, each with a verdict: 0 convertible / 25 not convertible / 5 pending, not one pair left blank. That table answers "can an electricity bill be converted into a water bill" — today's answer is: not by the platform itself.
The contract's "inspectable materials" list (six items): boundary statement, asset register, authorisation chain note, certification committee membership, public standard text, contract template placeholder.
The integration package note and field quick-reference sheet: the page you keep at hand while connecting.

5. Test vector download slot (compute it yourself first)

Three offline vectors that open and save with no network. Write for the originals; the expected verdicts are written here, so you can read the verdict first and then ask for the originals to recompute yourself.

Group A · one correct book　expected verdict: PASS (independently verifiable) — entry count, the two subtotals and the whole-ledger digest, computed live in three steps and identical to the declared values digit for digit.
Group B · one number changed　expected verdict: FAIL (altered) — naming entry 3, naming the "quantity" field, and stating the original and current value (1200 → 1201).
Group C · one entry removed　expected verdict: INCOMPLETE (this book is incomplete) — 5 entries declared, 4 present, and entry 4 is the missing one.
Recomputation notes: the three-step formulas, the intermediate values, the verdict. Standard library only; nothing to install.
Self-test script: computes the three groups live and prints the verdicts; the test is whether it catches the error, not whether it runs.

How to use: put the three inputs and the script in the same directory layout, run the script, and see whether it reaches the three verdicts above by itself. If it cannot produce B's "which entry, which field" or C's "which entry is missing", that group is not done — "it is wrong" is not a verdict, and reconciliation needs "which cell".

6. Three hard boundaries (said up front, to save argument later)

We do not issue certificates and do not define algorithms: a "certificate reference" is only a reference string in the ledger; the certificate algorithm, key length and signature algorithm are all "to be decided later by the security side" — today there is none.
We do not compute money: the endpoints record only the "how much was used" and the "original amount" that you report; no rate is applied, no tiers, no invoice. Split accounting and invoicing are a separate layer, and that layer's six commercial parameters are unconfirmed, so formal invoicing is currently always blocked.
We do not serve end users directly: end-user contracts, tariffs and service are provided by the national operating entities. We provide technology and standards, not a shopfront.

7. One mailbox

Access and material requests

partners@neutralorbit.com　(the address is live)

The address is fixed to partners@neutralorbit.com and the mailbox is active: mail sent to it is received. It is a clickable link on this page: click it and your mail client opens with the address already filled in.
When writing, say which document you need and what you want it for; replies may take a few working days.

8. How soon you can see something

No "fixed number of days" is promised — each stage runs from written confirmation by both sides, because the compliance and authorisation pace differs by country. What can be stated is the order:

First you get the three offline vectors and the recomputation notes: this step depends on nobody, and you can run it as soon as you have it.
Then discuss integration with the three write endpoints: the address is ready (see API status), credentials are issued by hand, so a confidentiality agreement comes first.
The test environment waits until it is built; no date is given for this item, and until then this page says "under construction".

Next step

Before you connect, verify: compute the three vectors yourself.

Go to Verify →