Skip to main content

​
SELAT Plugins for agent runtimes

Install SELAT in your agent harness to discover capabilities beyond the model’s built-in tools and pay for approved services from your own Circle Agent Wallet.
SELAT Plugins add an agent-runtime integration path for supported coding agents. They help compatible agents discover vetted skills first, then search a federated x402 and MPP service catalog when no vetted skill fits. The plugin layer wires the published @selat-ai/selat-cli runner into each host; Plugins and the CLI are agent-operator surfaces, not the TypeScript developer SDK. 1 2 The resulting workflow is designed for tasks such as web research, data enrichment, transcription, image, video, audio, or voice generation, real-time information, and on-chain actions when those capabilities are not already available in the agent runtime. Discovery is free. A paid execution begins only after the user has reviewed the price and approved the action. 1

​
Choose your agent harness

SELAT supports the following installation paths. Select the guide for the agent environment you already use; the underlying command runner remains the same across hosts. 1
Surface boundary: This guide configures supported agent runtimes. Use SELAT CLI when you operate from a terminal without a harness. Use the separate SELAT Router SDK documentation only when you are integrating paid requests into a TypeScript application. Do not combine SDK package or signer setup with this plugin installation flow. Prerequisite: The plugin and CLI require Node.js 18 or later. No Python installation is required. 1 2

​
Set up the runner

After installing a plugin, confirm that the runner and wallet configuration are ready. selat init checks the runner dependencies, Circle authentication, wallet configuration, and payment components. selat doctor provides a read-only diagnostic report when setup needs attention. 1 2
SELAT uses a Circle Agent Wallet for its self-custody path. The wallet’s signing material stays outside the SELAT plugin and agent context; the setup flow authenticates the wallet owner through Circle’s login process. 1 3

​
How SELAT discovers capabilities

SELAT uses a two-tier discovery loop so an agent can prefer reusable, evaluated workflows before considering a one-off endpoint. This reduces the need to hand-assemble payment calls while preserving a fallback for capabilities that are not yet packaged as skills. 1 Start with free discovery. selat search ranks candidates without a wallet signature or payment, while selat skill list --available lets you browse available reusable skills. Use a paid command only after evaluating the available option and cost. 1 2
For a complete description of reusable skills, their manifests, and per-step payment caps, see Skills. For a terminal-first walkthrough, see SELAT CLI.

​
Safety and custody boundaries

The plugin is deliberately conservative around wallets and money. It detects setup state and guides the agent, but it is not a wallet-provisioning or payment-authorizing shortcut. The following boundaries are material to a safe deployment. 1
Practical rule: Use free discovery first. Before any command that can spend, show the user what will be purchased and obtain an explicit go-ahead. 1

​
Choose the right SELAT surface

SELAT Plugins and the SELAT CLI serve agent and operator workflows. The SELAT Router SDK is a separate developer surface for TypeScript applications that integrate paid requests in code. Choose the surface that matches how you are working. 1 2 4
More questions? See the FAQ. For SELAT’s hosted discovery MCP, see Catalog MCP.

​
Next steps

Continue with SELAT CLI for the terminal workflow, browse Skills for reusable paid workflows, or build programmatically with the SELAT Router SDK.

​
References