LLM Reference
This section provides documentation optimized for Large Language Models (LLMs) to understand and use Vultrino effectively.
Quick Reference
What is Vultrino?
Vultrino is a credential proxy that allows applications (including AI agents) to make authenticated API requests without seeing the actual credentials.
Key Concept: You use credential aliases (like "github-api"), not actual secrets.
Available Paths
For programmatic access to documentation, these raw markdown paths are available:
| Content | Path |
|---|---|
| Full reference | /llm/full-reference.md |
| Quick start | /getting-started/quickstart.md |
| CLI commands | /components/cli.md |
| HTTP API | /api/http.md |
| MCP tools | /api/mcp-tools.md |
Condensed Reference
Making Authenticated Requests
Via HTTP Proxy:
curl -H "X-Vultrino-Credential: <alias>" \
http://localhost:7878/https://target-api.com/endpoint
Via MCP (AI Agents):
{
"tool": "http_request",
"arguments": {
"api_key": "vk_your_api_key_here",
"credential": "<alias>",
"method": "GET",
"url": "https://target-api.com/endpoint"
}
}
Via CLI (requires running Vultrino web server):
vultrino --key vk_your_api_key request <alias> https://target-api.com/endpoint
MCP Tools Summary
| Tool | Purpose | Required Permission |
|---|---|---|
list_credentials | List available credentials | read |
http_request | Make authenticated request | execute |
get_credential_info | Get credential metadata | read |
Important: Every tool call requires an api_key parameter for authentication.
Common Credential Aliases
Typical naming patterns:
github-api— GitHub API tokenstripe-live/stripe-test— Stripe API keysopenai— OpenAI API keyanthropic— Anthropic API keyaws-prod/aws-staging— AWS credentials
For AI Agents
Authentication Model: Every tool call requires your API key. This enables multiple agents to use the same MCP server with different scoped keys.
Step 1: Check Available Credentials
{
"tool": "list_credentials",
"arguments": {
"api_key": "vk_your_api_key_here"
}
}
Response:
{
"credentials": [
{"alias": "github-api", "type": "api_key", "description": "..."},
{"alias": "stripe-test", "type": "api_key", "description": "..."}
]
}
Step 2: Make Request
{
"tool": "http_request",
"arguments": {
"api_key": "vk_your_api_key_here",
"credential": "github-api",
"method": "GET",
"url": "https://api.github.com/user"
}
}
Response:
{
"status": 200,
"headers": {"content-type": "application/json"},
"body": "{\"login\":\"username\",...}"
}
Step 3: Parse Response
The body field is a JSON string. Parse it to access the data.
Error Handling
If a credential isn't available:
- List what IS available
- Explain to user
- Offer alternatives
Example response to user:
"I don't have access to AWS credentials. I can access: github-api, stripe-test. Would you like to add AWS credentials?"
HTTP API Quick Reference
Proxy Request
GET /https://api.example.com/endpoint
X-Vultrino-Credential: <alias>
Authorization: Bearer <vultrino-api-key> (if RBAC enabled)
List Credentials
GET /v1/credentials
Authorization: Bearer <vultrino-api-key>
Execute Action
POST /v1/execute
Authorization: Bearer <vultrino-api-key>
Content-Type: application/json
{"credential": "<alias>", "action": "http.request", "params": {...}}
Configuration Summary
Environment Variables
VULTRINO_PASSWORD— Storage encryption password (required)VULTRINO_CONFIG— Config file pathRUST_LOG— Log level
Default Ports
7878— HTTP proxy7879— Web UI
File Locations
~/.vultrino/credentials.enc— Encrypted credentials~/.vultrino/admin.json— Admin auth/etc/vultrino/config.toml— System config
Security Model
- Credentials encrypted at rest — AES-256-GCM
- Aliases only — Never expose actual secrets
- RBAC — Role-based access control via API keys
- Policies — URL/method restrictions
- Audit logging — Track all usage
API Key Authentication
Vultrino uses per-request API key authentication. Include your API key in every tool call:
{
"tool": "list_credentials",
"arguments": {
"api_key": "vk_your_api_key_here"
}
}
This design enables:
- Multiple agents using the same MCP server with different keys
- Scoped access - each key has its own permissions and credential access
- No session state - stateless, secure by default
The API key determines what credentials you can access based on your assigned role:
| Role | Permissions | Use Case |
|---|---|---|
executor | read, execute | AI agents (recommended) |
read-only | read | Listing credentials only |
admin | all | Full administrative access |
Every tool call requires the api_key parameter.
Common Tasks
"List my credentials"
{"tool": "list_credentials", "arguments": {"api_key": "vk_..."}}
"Get my GitHub user info"
{
"tool": "http_request",
"arguments": {
"api_key": "vk_...",
"credential": "github-api",
"method": "GET",
"url": "https://api.github.com/user"
}
}
"Create a Stripe customer"
{
"tool": "http_request",
"arguments": {
"api_key": "vk_...",
"credential": "stripe-api",
"method": "POST",
"url": "https://api.stripe.com/v1/customers",
"headers": {"Content-Type": "application/x-www-form-urlencoded"},
"body": "email=user@example.com"
}
}
"List GitHub repos"
{
"tool": "http_request",
"arguments": {
"api_key": "vk_...",
"credential": "github-api",
"method": "GET",
"url": "https://api.github.com/user/repos"
}
}