Vritanta AI
Ask about anything we make.
Try one
When you speak, your browser turns it into text, and it may send the audio to its maker's speech service (for Chrome, Google). Typing sends only the text, to this site.
We don’t keep your questions. When the full AI is on, your question and the matching passages from our pages go to Anthropic’s Claude to write the answer. How we handle questions.
One question, many doors.
Vritanta AI answers from this site and points you to the rest of what we build. Here is what it can reach, and what is not connected.
- Vritanta AI (this page)Live
Answers from this site’s published pages. Full AI writing can be switched on or off; the panel above says which.
Ask here - Site pagesLive
Products, the Clinic, capabilities, explainers, care and prices: the only things Vritanta AI reads.
All products - LabLive
53 free tools that run in your browser. Vritanta AI can point you to the right one.
Open the Lab - INDRALive
The back office where agents draft and you approve. Every action leaves a signed receipt you can check in the demo.
Open the INDRA live demo (opens INDRA) - MCP for other agentsLive
/api/mcp gives other people’s AI agents the same small tools, 100 free calls a day per address.
The MCP endpoint - Agent platformInternal
The research behind the receipts. Not connected to this page.
How it is built
Solid lines: live today. Dashed: internal, not connected to this page.
Agents draft. People approve. A kernel signs.
Under our products is one rule: agents draft, people approve, receipts prove it. We built a research platform to test that rule, and we keep it internal.
- Agent mesh · Elixir/OTP
- Each agent runs as a supervised process: if one crashes, its supervisor restarts it and the others carry on. It runs on our own server, for our own test agents. No customer uses it.
- Signing kernel · Rust
- It signs each agent action with an ed25519 key and links it to the one before, so a changed or missing record shows. It has signed 43,250 actions so far, all by synthetic test agents (as of 26 September 2026).
- In our products
- INDRA carries the same idea in its own code: every approved action leaves an ed25519-signed, hash-linked receipt you can check in its demo.
An agent drafts the action, a person approves it, the kernel signs it, and anyone with the public key can check the signature.
- Agent draftStep 1An agent drafts the action (an Elixir process)
- A personStep 2A person approves it
- Signed receiptStep 3The kernel signs it with ed25519
- SystemStep 4Anyone with the public key can check it
Source: our agent platform's design (internal); content/facts.yaml