# SELAT

SELAT is the buy-side of machine-native commerce. Paid data, scraping, media, compute, and on-chain actions become one purchase motion: the agent discovers paid capability sources at runtime, pays each provider natively on its own rail and chain, and records every purchase in one treasury ledger — under hard caps checked before spend.

## Core Pages
- Home: https://selat.ai/
- Docs: https://www.selat.ai/docs
- Blog: https://selat.ai/blog
- Manifesto: https://selat.ai/manifesto

## Homepage Map
- Hero: The buy-side of machine-native commerce. One purchase motion for paid capabilities agents discover at runtime, from one self-custody treasury with hard caps and one reconciled ledger.
- Access layer // Federated catalog: What your agent can't do yet is one paid call away. The catalog lives in the terminal through free discovery before wallet setup or spend.
- Capability categories: scraping, data enrichment, media generation, real-time data, on-chain actions.
- How it works // One purchase motion: Discover, fund, authorize, execute, reconcile — federated discovery with live pricing, one funded treasury, caps checked before every signed payment, provider-native settlement, and one ledger.
- Provider choice // Buyer simplicity: The provider picks the rail; the agent doesn't care. x402, MPP, or the next machine-payment protocol each settle on their own chain while drawing from one treasury.
- Execution path // Chained capabilities: Every AI workflow becomes a purchasing workflow. A chained run buys from multiple providers in sequence — each step quoted and capped — and returns one result with itemized receipts reconciled in one ledger.
- Insights & Tutorials: blog posts on agentic payments, x402, MPP, multi-rail routing, and agent wallets.

## Community
- GitHub: https://github.com/SELAT-AI
- X: https://x.com/selat_ai
- LinkedIn: https://www.linkedin.com/company/selat-ai

## Plugin Installs
- Marketplace repo: https://github.com/SELAT-AI/selat-plugins
- Prefer plugin installs for supported harnesses. Use the direct CLI install only when a harness plugin is unavailable.
- Discovery commands such as `selat search` are free. Commands that spend or move funds require explicit user approval.
- Start by asking the agent to read https://selat.ai/llms.txt and install the SELAT plugin for its harness.

### Claude Code
```bash
claude plugin marketplace add SELAT-AI/selat-plugins
claude 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.
- Then allowlist SELAT in `.cursor/sandbox.json` as described in 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 --auto-update
```

### OpenClaw
```bash
openclaw plugins install selat --marketplace https://github.com/SELAT-AI/selat-plugins
```

### Other Harnesses
```bash
npm i -g @selat-ai/selat-cli
```

## Blog
- Why AI Agents Break the Moment a Task Needs Payment: https://selat.ai/blog/why-agents-break-at-payment - Agents can discover services mid-task but stall when payment starts — no runtime payment surface, no shared credentials, no unified liquidity. Here's why agents break at payment, and what closes the gap.
- Multi-Rail Agent Payment Routing: One Wallet, Every Rail: https://selat.ai/blog/multi-rail-agent-payment-routing - As agent payment rails multiply — x402, MPP, Circle Gateway — builders pay an integration tax that grows with each one. Here's the case for rail-neutral routing: one wallet, one signature, every rail.
- x402 vs MPP: Which Agent Payment Protocol Should You Use? (2026): https://selat.ai/blog/x402-vs-mpp - x402 and MPP both let AI agents pay for APIs over HTTP 402 — but they settle differently. A builder's comparison of rails, costs, and when to use each (or both).
- How AI Agents Pay for APIs: A Builder's Guide to Agentic Payments: https://selat.ai/blog/how-ai-agents-pay-for-apis - AI agents can now pay for APIs, data, and compute mid-task — no human checkout. Here's how agentic payments actually work, from HTTP 402 to wallets, rails, and spending limits.

## Primary Topics
- Paid capability access for AI agents
- Federated runtime catalog
- Settled skills
- Agent treasuries and spend caps
- Agentic payments
- HTTP 402 Payment Required
- x402 and MPP payment protocols
- Multi-rail payment routing
- Agent wallets