rest-api

A REST API for Forklift inventory data, such as virtual machines, networks, storage, and hosts. A REST API is a web interface that lets software request and use data through defined URLs.

In plain words
What is it for?
It helps expose inventory services over a secured connection, with provider routes, authentication-related setup, pagination, and web server configuration.
Why use it?
It gives the frontend a consistent way to retrieve provider details, choose virtual machines, and configure mappings.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/kubev2v/forklift-console-plugin/rest-api
Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.04019
Opus 5 $0.00010 $0.02010
Sonnet 5 $0.00004 $0.00804
Haiku 4.5 $0.00002 $0.00402

Measured 2d ago against content hash 0c49a113f63e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rest-api scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/backend/infrastructure/rest-api.mdc · 396 lines

How it starts

The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forklift Inventory REST API

The forklift-api process runs an inventory REST API over TLS on port 8444. It exposes provider inventory data (VMs, networks, storage, hosts, etc.) collected by the inventory controller. The frontend plugin queries these endpoints for provider details, VM selection in plans, and mapping configuration.

Source: pkg/controller/provider/web/ and pkg/forklift-api/services/ in the forklift repo.


Server Setup

pkg/forklift-api/api.go  →  ForkliftApi.Execute()
  ├── goroutine: serveServices()   → :8444 (REST services + inventory)
  └── serveWebhooks()              → :8443 (webhooks, see webhooks.mdc)
  • Port: 8444
  • TLS: Certificates from env vars SERVICES_TLS_CERTIFICATE and SERVICES_TLS_KEY
  • Framework: gin-gonic/gin for inventory routes; plain net/http.ServeMux for service endpoints
  • Router: Inventory handlers register via AddRoutes(*gin.Engine)

Service Endpoints (port 8444, ServeMux)

Path Method Handler Purpose
/tls-certificate GET serveTlsCertificate Fetches TLS certificate from a remote URL

TLS Certificate Service: Accepts a ?URL=<url> query parameter, connects to the URL with insecureSkipVerify, retrieves the server's TLS certificate, and returns it as PEM-encoded text/plain. Used by the UI to auto-discover CA certificates during provider creation.


Inventory REST Endpoints (port 8444, gin)

Inventory read endpoints are GET-only. The base path is /providers. Provider utility/operation endpoints (e.g., VDDK image upload) may use other HTTP verbs.

Cross-Provider Endpoints

Route Description
GET /providers Lists all providers across all types, grouped by provider type
GET /providers/ Same as above

The aggregated /providers endpoint queries each provider-type handler and returns:

{
  "openshift": [...],
  "vsphere": [...],
  "ovirt": [...],
  "openstack": [...],
  "ova": [...],
  "hyperv": [...],
  "ec2": [...]
}

Read the full file on GitHub · 396 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 396 lines · 20 tokens per session scan A 0c49a113f63e

Subscribe to this mod's changes

rest-api is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 4,019 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.