NectarBox features and progress
NectarBox gives your apps, scripts and bots one private door to AI models. The first version runs on our test system with private models only; we are moving sign-in, keys and settings to IT-Labs Core, so one account and one keys page can work for every IT-Labs product (planned).
- 18 Ready
- 13 In testing
- 4 Planned
Ready: built and passing its tests on our development system. In testing: built and in testing; anything that does not pass testing will be removed. Planned: not built yet; no date promised.
One door for your apps
-
Standard chat API
ReadyApps that already speak the common chat API work by changing only the address and the key.
-
Answers that follow your JSON schema
ReadyGet answers in the exact structure your app needs, ready to save or process.
-
Streaming answers
ReadyShow the answer as it is written, so users do not wait for the whole text.
-
A default model name
ReadyApps just ask for "default"; your organisation decides which model answers.
-
List of available models
ReadyYour app can see which models your organisation allows.
-
Routing per purpose with a fallback
ReadyIf one model is busy or fails, the next one answers, without changes in your app.
-
A fair queue when models are busy
ReadyBusy times slow requests down evenly instead of failing some of them.
-
Embeddings for search
PlannedSearch and match your own documents through the same door.
-
Many model machines behind one address
In testingYour calls go to the best free machine that is allowed for you, so answers come faster and one busy machine does not stop your work. Your apps change nothing.
-
Choose which machines may answer
In testingYour organisation or client can rule out kinds of machine, for example rented ones, so your text only goes where you allow it.
Keys for every app
-
Its own key for each app, script or bot
ReadyEach AI call is tied to one person's key. Showing the app name for keys made on IT-Labs Core is still being built.
-
Switch a key off at once
ReadyStop a misbehaving app in one click and turn it back on when it is fixed.
-
Replace or revoke a key
In testingA leaked key is replaced or switched off on IT-Labs Core without touching your other apps.
-
Limits per key
ReadySet requests per minute, daily volume and parallel calls for each app.
-
Hand an app over to a colleague
PlannedWhen someone changes role, their apps move to a colleague; this returns on IT-Labs Core.
-
One API keys page for apps that call NectarBox
In testingCreate named keys on IT-Labs Core for apps that call NectarBox. Showing the key name on the Usage page is still being built.
Private by default
-
Private models only
ReadyYour text is answered on our own model servers and is not sent to an outside AI company.
-
Client walls
ReadyBuilt so that one client's requests, records and costs never reach another client.
-
No text stored unless you switch it on
ReadyBy default only who, when and how much is kept, never the prompts or answers.
-
Your own text log, when you want one
ReadySwitch the log on for an app to check its answers, then read or delete it from your IT-Labs account page; only you see that text.
-
Staff manage but never read
ReadySupport staff can set up accounts and limits but cannot see your prompts or answers in normal operation; not independently audited.
-
Larger outside models, only by your choice
PlannedUse bigger models when you and your client agree, with e-mails, phone numbers and account numbers masked first.
Usage and limits
-
Usage per app and per person
ReadySee calls and volume per key on the Usage page; app names for IT-Labs Core keys are still being built.
-
Daily caps for the organisation
ReadyA call past the limit you set is refused.
-
Activity record without the text
ReadyAnswer "who used AI on what, and when" without keeping the content.
-
Usage reported for billing
In testingDaily usage totals are sent to IT-Labs Core so that billing can later use real usage. No plans or prices are set yet.
-
A spending limit per task
In testingGive a piece of work a name and a token limit; it stops at that limit even if the app keeps asking.
-
Usage and cost reports in IT-Labs Core
In testingSee this month's calls, volume and cost per person, model, task and team; the numbers come live from NectarBox and your text never leaves it.
-
Organisation settings in one place
In testingDaily limits, allowed models and the text log rule are set on IT-Labs Core's rules page; the stricter setting is meant to win.
Sign-in and accounts
-
One IT-Labs sign-in
PlannedSign in once at IT-Labs Core and open NectarBox and your other IT-Labs products without another password.
-
Confirm important changes
In testingRaising limits or switching an app back on asks you to confirm your sign-in again, so a left-open browser is not enough.
-
Keeps working if the main sign-in is briefly down
In testingA short outage at IT-Labs Core does not stop you; NectarBox shows a notice and keeps your session for a while.
-
Managed together with your other IT-Labs products
In testingAccounts, seats and settings are set up in one place for all IT-Labs products, and NectarBox keeps working on its own.
Help where you need it
-
First-use guide and help page
In testingThe first screen tells you what to do next and shows an example call for your first app.
-
Short plain-word manuals
In testingStep-by-step guides for signing in, creating a key and connecting an app.
Suggest a feature
Something NectarBox should do for your business? Tell us; the founder reads every suggestion.