Memory that supersedes
A customer moves from Growth to Enterprise. Both facts were true once; one is true now.
Three engines benchmarked.
All three quoted the cancelled plan.
Memory that knows when a fact has changed, traces that name the tool that got it wrong, and cost attributed to the customer who caused it. You call it; we run it.
1,000 runs free · no card · unlimited seats on every plan
Answers tickets from the handbook and the customer's own order history.
Reads an invoice, posts it, and stops at an approval before anything ships.
Fans a question across sources and returns one brief with citations.
Walks a new account through setup, remembering what they already did.
The difference
Tracing tools attach to an agent you host and hand back a waterfall. The memory is still yours to build, so is the retrieval, the tenant boundary, the version history and the machine it runs on.
A customer moves from Growth to Enterprise. Both facts were true once; one is true now.
Three engines benchmarked.
All three quoted the cancelled plan.
Tool arguments, results, tokens per turn, and where each tool came from.
33 event types · 14 categories
Priced per call, summed onto the run, the conversation and the user.
Six decimals · avg $0.00215
A tool's tags are the server's claim about itself. The MCP specification is explicit that a server can declare readOnlyHint: true and delete your files anyway — so tags decide nothing here. Nixet resolves your policy before the model is ever offered the tool.
Deny is deny, whatever the server says.
Twelve formats, converted locally in Rust, embedded on a worker you can watch.
Memory
Nothing marks the old fact as no longer true, so the agent picks whichever the retriever ranked highest — and quotes the cancelled plan back at the customer paying for the new one.
Control
A model that can call a tool will eventually call the wrong one. Every mechanism here refuses something before it happens, on the Nixet side, where a prompt cannot argue with it.
A server's tags are its own claim. The MCP specification says plainly that it can declare readOnlyHint: true and delete your files anyway, so the policy you wrote is what runs.
Twenty-two detection labels across four modes. The provider receives a token where a name was, and the answer is restored on the way back out.
A customer's URL is resolved to an address and checked against private ranges — then checked again on every redirect, because a public link that 302s to the metadata endpoint is the whole technique.
A workspace that has used its allowance is refused at admission, before the model is paid for. Runs already executing finish; nothing is killed mid-flight.
A tool tagged destructive pauses the run and waits for a person. Today that policy is refused at publish rather than stored, because an agent that cannot stop should not claim it will.
Run a published version against a dataset in a sandbox, score it, and compare it to the version it replaces — so a prompt change is a measurement rather than a hope.
Trust
An agent reads whatever your customer typed, and most of what they type is personal. Nixet masks it before the model provider sees it, keeps the original encrypted, and records who looked.
22 detection labels across four modes. The provider receives a token where a name was.
Masked values go to an AES vault keyed per deployment. Postgres never holds the plaintext.
Memory and knowledge are keyed to your customer. A partial key addresses nothing, not more.
Key issuance, revocation and every reveal of a masked value, with the member who did it.
EU region, a signed DPA, and deletion that reaches the vault and the vector store.
Audit underway. We will say so here when the report exists, and not before.
What the provider actually receives
The agent reasons over tokens and the answer is restored on the way out, so the customer reads their own name and the provider never saw it.
Pricing
A run is one question answered, one ticket triaged, one document processed — a number already visible in your own product. No per-seat fee, no per-connection fee, no charge for the second person to look at a failure.
* SOC 2 Type II audit is in progress. Redaction, the encrypted vault, tenant isolation and the audit trail ship today on every plan.
The console is where you go when something went wrong. Charging for the colleague you show the trace to is charging for incident response, so we don't.
Point Nixet at your provider key and pay the platform fee, nothing else. If you'd rather we ran the gateway, managed inference is +15% on Pro and +8% on Scale.
$0
A month of real development at the measured rate.
Start free$29 /mo
The plan a team of two is already past the point of.
Start building$249 /mo
Half a million runs, a year of traces, an SLA to point at.
Start buildingCustom
A committed rate, SSO, and an engineer who knows you.
Talk to usStart
Create an agent, publish a version, and watch the first run land in the console.
1,000 runs free · no card