DEVELOPERS
One endpoint. One key. One stream.
SICILEE is a single HTTPS call that streams its answer back as it is written. If you have integrated any modern model, you already know the shape.
Authorization: Bearer ••••••••
Accept: text/event-stream
{ "message": "...", "context": "..." }
Events arrive as they are generated. Nothing waits for the whole answer, because nothing downstream needs it whole.
It identifies your company, not your user.
Your key belongs on your server and never in a browser. If you send an end user identifier, it must come from a session you verified, never from a field the browser can set.
Keys expire and can be rotated or revoked without downtime.
Stateless is what you get.
Send the conversation you want considered. Nothing is read from memory and nothing is written to it, so there is no data custody conversation to have with your legal team.
Resident mode, where SICILEE keeps memory, runs our own products. If you need it, it is a flag on your organisation and not a change to your code.
Actions are reviewed
If you give SICILEE tools, Guardian rules on what each one would do before it runs. You decide what needs a person.
Errors are structured
Every failure arrives as a code you can branch on. Nothing hands you a stack trace or a wall of prose to parse.
Tenants are separated
A request that cannot name its organisation is rejected rather than defaulted. Isolation is enforced where the data lives.
Talk to us before you build.
Access is granted per company. Tell us what you are building and we will set up your organisation.
[FULL REFERENCE NOT PUBLISHED YET]