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:

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": {
    "credential": "<alias>",
    "method": "GET",
    "url": "https://target-api.com/endpoint"
  }
}

Via CLI:

vultrino request -c <alias> https://target-api.com/endpoint

MCP Tools Summary

Common Credential Aliases

Typical naming patterns:

• github-api — GitHub API token
• stripe-live / stripe-test — Stripe API keys
• openai — OpenAI API key
• anthropic — Anthropic API key
• aws-prod / aws-staging — AWS credentials

For AI Agents

Step 1: Check Available Credentials

{"tool": "list_credentials", "arguments": {}}

Response:

{
  "credentials": [
    {"alias": "github-api", "type": "api_key", "description": "..."},
    {"alias": "stripe-test", "type": "api_key", "description": "..."}
  ]
}

Step 2: Make Request

{
  "tool": "http_request",
  "arguments": {
    "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:

1. List what IS available
2. Explain to user
3. 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 path
• RUST_LOG — Log level

Default Ports

• 7878 — HTTP proxy
• 7879 — Web UI

File Locations

• ~/.vultrino/credentials.enc — Encrypted credentials
• ~/.vultrino/admin.json — Admin auth
• /etc/vultrino/config.toml — System config

Security Model

1. Credentials encrypted at rest — AES-256-GCM
2. Aliases only — Never expose actual secrets
3. RBAC — Role-based access control
4. Policies — URL/method restrictions
5. Audit logging — Track all usage

Common Tasks

“List my credentials”

{"tool": "list_credentials", "arguments": {}}

“Get my GitHub user info”

{
  "tool": "http_request",
  "arguments": {
    "credential": "github-api",
    "method": "GET",
    "url": "https://api.github.com/user"
  }
}

“Create a Stripe customer”

{
  "tool": "http_request",
  "arguments": {
    "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": {
    "credential": "github-api",
    "method": "GET",
    "url": "https://api.github.com/user/repos"
  }
}