TEKIMAXALOS

The whole platform, typed, in your code.

Everything the product does is open to your own code, with the types already written for you. The client SDK is built from the same description the API itself is built from, so when one changes the other changes with it, and your editor tells you where before anything runs.

one person working at a laptop in strong daylight

One description, and everything comes from it

The API is described once, in a file a machine can read, and that description carries the governance facts for every single operation: which role it needs, whether it can be undone, whether it is recorded, and what data it touches. The SDK, the reference documentation and the access diagram you can open on any operation are all built from that one file.

Written for the language you build in

The one that ships in the box is TypeScript: a friendly layer for each thing in the product, a plain layer underneath for anything else, and the same governed tools an AI agent uses, with the same reason required. Versions for Python, Go and Rust, and a build for mobile apps, are generated from your organisation's own live API and delivered as downloads.

A short TypeScript sample: create the client with a token read from the environment and a default reason, then list the skills for Northwind Robotics

Safe in a browser or a phone

A build meant for a browser or a phone never carries a real key. It holds one that opens nothing on its own, and can only be traded, together with a human who is signed in at that moment, for a short-lived pass that belongs to that one human rather than to the whole organisation.

Given to clients, not published

The SDK is ours and is given to clients as part of an engagement, as a numbered download tied to your own sign-in. It is a client SDK, licensed for your use of the platform, and it is not a public library you can pull off the internet.

The API itself

Every call is signed in as exactly one organisation, worked out on the server. A caller never gets to say which organisation it is for. Writing anything needs the right role. Permanent operations refuse a machine sign-in outright, and several of them offer a dry run that tells you what would happen without doing it. Calls worth retrying take a key that stops the same request running twice.

The SDK comes with an engagement. Ask us for access.

Talk to us