janus-kinematic-drive
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JANUS_URL | No | The URL of the Janus concierge server | https://api.welcome-to-ubos.com/janus |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| janus_askA | Ask Janus, the UBOS Kinematic Drive concierge, anything about getting or using a private Kinematic Drive (what it is, pricing, privacy, how to connect your agent). Grounded on real product knowledge and live data. |
| kinematic_pricingA | Get the current Kinematic Drive pricing (live source of truth). |
| kinematic_statusA | Check whether a Kinematic Drive instance is up and running. |
| kinematic_provisionA | Request a private Kinematic Drive (managed onboarding). Records the request; the UBOS team mints an isolated drive for you. No charge or spin-up happens from this call. |
| kinematic_checkoutA | Buy a private Kinematic Drive with USDC, fully self-serve. Creates an order and returns payment instructions (Solana wallet + memo + amount). Send the USDC with the memo EXACTLY as given, then poll kinematic_checkout_status until it returns your provision token. No card, no account — pure on-chain. |
| kinematic_checkout_statusA | Check a Kinematic Drive checkout order: pending (with pay instructions) or paid (with your provision token). |
| ubos_store_productsA | List the UBOS x402 metered tools any agent can pay-per-call with USDC — e.g. governor (constitutional reality-check of an action, $0.005/call) and hotvessel (metered LLM completion, $0.01/call). |
| ubos_store_callA | Call a UBOS x402 metered tool, pay-per-call. Choose any api_key string as your agent identity; with no balance you receive HTTP-402 pay instructions (send USDC on Solana to the wallet with memo = your api_key; credits in ~15s; retry). governor payload: {"action": "..."}; hotvessel payload: {"prompt": "..."}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct: provisioning, checkout, checkout status, instance status, pricing, store listing, store calling, and concierge all map to different actions. The main potential confusion is between kinematic_checkout and kinematic_provision (both lead to getting a drive) and between kinematic_checkout_status and kinematic_status, but the descriptions clarify the differences well.
The server uses consistent snake_case and useful prefixes like kinematic_ and ubos_store_, but the naming style is mixed: some tools are verb-led (kinematic_provision, kinematic_checkout), while others are noun-led (kinematic_pricing, kinematic_status). The pattern is readable and scannable, but it is not a uniform verb_noun convention.
Eight tools is a well-scoped set for this server's purpose. Each tool covers a distinct aspect of Kinematic Drive access, checkout, status, pricing, and UBOS store usage, with no obvious bloat or excessive granularity.
The core lifecycle is covered: request, checkout, checkout status, instance status, pricing, and concierge support. Minor gaps exist, such as no explicit cancellation or deprovisioning tool and no direct status endpoint for a provision request, but these are workable gaps given the concierge and live data grounding.