Bring the workflow. We provide the model.
A private path.
In your own tools.
Use Veilo Protocol from an AI assistant, a local document connector, or your application. Every analysis follows the same review boundary.Use the web workspace
Veilo Protocol provides the model. Create a temporary access key for your assistant or application.
Keys expire after one hour. A new key revokes this browser’s earlier key. Model credentials stay on the server.
{
"mcpServers": {
"veilo": {
"url": "https://www.veilo.fun/api/mcp/",
"headers": {
"Authorization": "Bearer YOUR_VEILO_ACCESS_KEY"
}
}
}
}Add a Streamable HTTP server in a compatible MCP client. Client configuration formats differ; the URL and Authorization header above are the required values.
Review links work in the browser that created your key. Keep them private and approve personally. Local masking is best effort; cloud analysis sends approved text to Veilo Protocol and its model provider. MCP results may also reach your assistant’s provider.
From connection to a reviewed result.
- 01Prepare your source
Select files and mask common secrets locally, or prepare text in your application.
- 02Review the plan
The model receives the goal first. Open the private review link and preview the exact prepared text.
- 03Approve and analyze
Your client sends the approved text, receives the report, and checks its fingerprint.
Connection keys last one hour and approvals last fifteen minutes. The hosted service shares approval and quota metadata across server instances. Prepared source text is sent to the model only after approval.