Install Jentic One Beta

Connect the Houston (vsc pool) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Houston (vsc pool), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrainq.com%2Fbrainq" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrainq.com%2Fbrainq" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Houston (vsc pool) API.

List and create compute nodes, read one node's details, and patch a node's configuration

List the VMs on a node and read a single VM's details

Read a VM's events, metrics, traffic usage, and uptime

Read node-level events, metrics, traffic usage, uptime intervals, and the service-level indicator

List releases for a target, check the current version, and download a release file

GET STARTED

Start building with Houston (vsc pool) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Houston (vsc pool) API for, with concrete tasks.

★ Fleet and VM Monitoring

Keep a view of a compute pool without logging into a console. An agent lists nodes, opens one node's VMs, and reads each VM's metrics, uptime, and traffic usage, then rolls the node-level uptime intervals and service-level indicator into a status report. This turns raw fleet telemetry into an answer an agent can act on.

List nodes, open one node's VM list, and read each VM's metrics and uptime

Node Provisioning and Release Checks

Grow or update a pool programmatically. An agent creates a node, patches its configuration, then lists releases for a target, checks the current version, and downloads the right release file. The release operations let the agent confirm it is deploying the expected build.

Create a node, patch its configuration, then list releases for the target and check the current version

AI Agent Integration via Jentic

An AI agent discovers and calls the Houston API through Jentic without handling the API key directly. The agent searches by intent, receives the matching operation and its input schema, and reads node or VM telemetry while Jentic injects the stored key in the Authorization header. This gives the agent fleet visibility without reading the reference docs or holding secrets.

Search Jentic for 'list nodes', load the operation schema, and read node details with Jentic-injected credentials

Key Endpoints

21 endpoints — the houston api manages compute nodes and the virtual machines that run on them.

METHOD

PATH

DESCRIPTION

GET

/nodes

Get the list of nodes

POST

/nodes

Create a new node

GET

/nodes/{xid}

Get node details

PATCH

/nodes/{xid}

Patch a node

GET

/nodes/{node_xid}/vm

Get the VM list for a node

GET

/releases/{target}

Get the list of releases for a target

GET

/nodes

Get the list of nodes

POST

/nodes

Create a new node

GET

/nodes/{xid}

Get node details

PATCH

/nodes/{xid}

Patch a node

GET

/nodes/{node_xid}/vm

Get the VM list for a node

GET

/releases/{target}

Get the list of releases for a target

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Houston API by hand means obtaining a key, sending it as a Bearer token in the Authorization header against houston.brainq.com, and polling node and VM telemetry yourself. Through Jentic you install once, import Houston from the API Directory, store the key once, and your agent calls it.

Permission scoping

Houston puts the node id in the URL path, so a rule can pin your agent to one node and the operations you pick, such as reading its metrics and uptime, while leaving node creation and configuration patching out of the set.

Credential isolation

Your Houston API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list nodes' or 'read a VM's metrics', and Jentic returns the matching Houston operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Houston (vsc pool) API through Jentic.

What authentication does the Houston API use?

The Houston API authenticates with an API key sent as a Bearer token in the Authorization header, per its OpenAPI spec. Every node, VM, and release operation expects that header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent.

Is there a Houston MCP server?

You do not need a separate MCP server to give your agent the Houston API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls its node and VM operations on demand. Operations are discovered as needed, so no extra server's tool definitions load into the agent's context.

Can I read a VM's metrics with the Houston API?

Yes. List a node's VMs, then read a single VM's metrics, events, traffic usage, and uptime. The responses are structured JSON an agent can summarise into a status report.

Can I limit what my agent is allowed to do with the Houston API?

Yes. Houston puts the node id in the URL path, so with Jentic you can pin the agent to one node and allow only the reads it needs, such as metrics and uptime, while withholding node creation and configuration patches. Because you run Jentic One yourself, every call the agent makes is logged.

How do I list nodes with the Houston API through Jentic?

Search Jentic for 'list nodes' to get the matching Houston operation and its input schema, then your agent calls it and reads each node's details. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Brainq Houston (vsc pool)

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Community OpenAPI document · agent-readyCloud InfrastructureComputeapiKey21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List and create compute nodes, inspect their VMs, and read metrics, uptime, and release files, across 21 endpoints secured with an API key in the Authorization header.

Use for: List the nodes in my pool, I need to create a new node, Get the details of one node, Retrieve a VM's metrics and uptime

Not supported: Does not handle billing, DNS, or object storage. Use for managing compute nodes and their virtual machines only.

The Houston API manages compute nodes and the virtual machines that run on them. It lists and creates nodes, reads a single node's details, and patches a node's configuration, then exposes each node's VMs along with their details, events, metrics, traffic usage, and uptime. Node-level reads cover events, metrics, traffic usage, uptime intervals, and the service-level indicator. It also lists software releases for a target, checks the current version, and serves release files for download.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

73%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Houston (vsc pool) to your agent

Capabilities

Start building with Houston (vsc pool) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Brainq Houston (vsc pool)

Jentic AI Readiness Score

Houston (vsc pool)

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness