# SELAT > SELAT turns intent into settled calls. It lets an agent discover a paid capability, inspect the price before spend, complete an approved purchase on the provider-supported rail, and reconcile the result in one ledger. SELAT treats agents as first-class customers. Free discovery comes first; wallet creation, funding, policy changes, and paid execution require the user's explicit approval. SELAT never holds user keys or funds. ## Core Pages - [Home](https://selat.ai/): product positioning, safe setup prompt, runtime proof, rail abstraction, the Transactability Index, and reusable skills. - [Docs](https://selat.ai/docs): installation, CLI reference, catalog, SDK, and skills. - [NEWS](https://selat.ai/news): official announcements and releases. - [TUTORIALS](https://selat.ai/tutorials): capability-driven agent workflows. - [INSIGHTS](https://selat.ai/insights): research and analysis of agentic commerce, including first-party comparisons of SELAT against alternatives. - [FAQ](https://selat.ai/faq): concise answers on custody, caps, paid capabilities, and agent payments. - [Transactability Index](https://selat.ai/transact): internal dashboard for SELAT's endpoint reliability signal; gated, not public. The public reading guide lives in the docs, and scores are readable for free via `selat search` and a --probe-only live probe — no account needed. - [Manifesto](https://selat.ai/manifesto): why machine economies need a passage rather than another destination. ## Homepage Map - Hero: the problem framing is that agents stall at paywalls. A copyable setup prompt sits under the headline and explicitly prioritizes free discovery and user approval before wallet or paid actions. - Runtime proof: a terminal-style run shows free discovery, a visible quote, policy check, approved execution, and a returned response. - Rail abstraction: one funded balance pays any provider, across x402 and MPP, without wiring up a rail. An illustrative paid run records endpoint-level prices, the rail each call settled on, balance consumed, remaining balance, and a reconciled result. - Transactability Index: a score for every merchant, built from runs SELAT observed rather than merchant self-reports, readable before the agent pays. - Reusable skills: recurring agent workflows become controlled purchasing flows; vetted skills are listed and run from the CLI, and a skill carries the capability, price context, and record with the task. ## Safe Operating Default - Start with `selat doctor` and `selat search ""`. Discovery is free and does not require a wallet or spend. - Use `selat run "" --dry-run` to inspect the selected capability and price without paying. - Do not create or initialize a wallet, fund an account, use an onramp, change policy, or run a paid command unless the user explicitly approves that action. - Treat the user's spending caps and per-call quote as approval boundaries, not as defaults to override. ## Catalog SELAT discovers paid capabilities across x402 and MPP sources at runtime. The hosted discovery MCP at `https://catalog.selat.ai/mcp` provides search and quotes; spend stays local. `selat search ""` queries and ranks from the CLI and costs nothing. A machine-readable catalog dump is available at `https://catalog.selat.ai/api/v1/federated`. Its JSON envelope contains a gzip-compressed, base64-encoded `data` payload; use the declared `compression`, `encoding`, and `generatedAt` values when decoding and refreshing a local cache. ## Community - [GitHub](https://github.com/SELAT-AI): open-source plugins, CLI, and skills. - [LinkedIn](https://www.linkedin.com/company/selat-ai) ## Plugin Installs - Marketplace repository: https://github.com/SELAT-AI/selat-plugins - Prefer plugins for supported harnesses. Use the direct CLI installation only when a harness plugin is unavailable. - Start by asking the agent to read https://selat.ai/llms.txt and follow the applicable harness guide. ### Claude Code ```bash claude plugin marketplace add SELAT-AI/selat-plugins claude plugin install selat@selat-plugins ``` In-session equivalent: `/plugin marketplace add SELAT-AI/selat-plugins` then `/plugin install selat@selat-plugins`. ### Codex ```bash codex plugin marketplace add SELAT-AI/selat-plugins codex plugin add selat@selat-plugins ``` ### Cursor - Use Cursor Customize → Marketplace or ask the agent to read https://github.com/SELAT-AI/selat-plugins and follow the Cursor guide. - Required: allowlist SELAT in `.cursor/sandbox.json`. Cursor's agent sandbox denies outbound traffic by default; see https://github.com/SELAT-AI/selat-plugins/blob/main/guides/cursor.md. ### Gemini CLI ```bash gemini extensions install https://github.com/SELAT-AI/selat-plugins ``` ### OpenClaw ```bash openclaw plugins install selat --marketplace https://github.com/SELAT-AI/selat-plugins ``` ### Hermes ```bash hermes plugins install SELAT-AI/selat-plugins/plugins/selat-hermes --enable ``` The subdirectory path is required; the bare repository form installs the plugin to the wrong location. ### Other Harnesses Install the reviewed pin, never `@latest`: the payment runner must be the version SELAT has vetted, and `--ignore-scripts` keeps package lifecycle scripts from running. ```bash npm i -g @selat-ai/selat-cli@0.17.5 --ignore-scripts ``` The authoritative pin is `plugins/selat/hooks-handlers/selat-cli.version` in https://github.com/SELAT-AI/selat-plugins; check it if the version above looks older than the published release. Prefer a harness plugin where one exists — those install the reviewed pin and lockfile for you. ## After Installing - `selat doctor` — confirm the installation and local configuration before any paid action. - `selat search ""` — free discovery and ranking across the catalog; no wallet and no spend. - `selat run "" --dry-run` — inspect the selected capability and price without paying. - Only after explicit user approval: `selat init` for wallet/config setup; `selat setup-policy` for caps; `selat fund` or `selat fund --onramp` for funding; and `selat run ""` for a paid execution. - Vetted multi-step skills come first: `selat skill list`, then federated discovery for work they do not cover. ## Editorial ### NEWS - [NEWS archive](https://selat.ai/news) ### TUTORIALS - [TUTORIALS archive](https://selat.ai/tutorials) - [Pay Exa from Your Agent — No API Key, One Install](https://selat.ai/tutorials/pay-exa-from-your-agent): Exa is an AI-native web search API. Your agent can call /search and /contents per request with no API key, paying from one balance across three rails. - [Pay Nansen from Your Agent — No API Key, One Install](https://selat.ai/tutorials/pay-nansen-from-your-agent): Nansen's on-chain analytics API, paid per call from your agent's own wallet. 72 endpoints, no API key, one balance across four rails — smart money to perps. - [Pay Tavily from Your Agent — No API Key, One Install](https://selat.ai/tutorials/pay-tavily-from-your-agent): Your agent can call Tavily search, extract, map, and crawl per request with no API key — paid from one wallet balance, across x402 on Base and MPP on Tempo. ### INSIGHTS - [INSIGHTS archive](https://selat.ai/insights) - [SELAT vs Skyfire](https://selat.ai/insights/selat-vs-skyfire): Skyfire is an agent identity and checkout stack for buying from websites. SELAT is a runtime payment layer for paying machine-native API endpoints per call. Different jobs — here is an honest map of which one fits yours. - [Counterparty Risk in Agentic Payments: The Unmeasured Half](https://selat.ai/insights/counterparty-risk-agentic-payments): Agent-payment infrastructure restrains AI agents but does not protect them as buyers. Why counterparty risk, not authorization, is the real adoption blocker — and what sell-side measurement would fix. - [Why Do AI Agents Break the Moment a Task Needs Payment?](https://selat.ai/insights/why-agents-break-at-payment): Why AI agents stall at HTTP 402 Payment Required: no runtime payment surface, no shared credentials, no unified liquidity — and what closes the gap. - [How to Let AI Agents Pay for APIs and Get Past Paywalls Automatically](https://selat.ai/insights/how-ai-agents-pay-for-apis): Autonomous AI agents get past paywalls by paying them: an HTTP 402 paywall is built for machine payment. How to let your agent pay for APIs automatically, settle in USDC from a self-custody wallet, and stay inside hard spending caps. ## Primary Topics - Paid capability access for AI agents - Controlled purchase flows and safe agent spending - Federated runtime discovery - Self-custody agent wallets, caps, and reconciled ledgers - HTTP 402 Payment Required, x402, and MPP - Endpoint transactability and counterparty risk