{"id":"ai.rokha/rokha","slug":"ai-rokha-rokha","title":"Rokha","description":"Search a registry of agent skills and MCP servers, then run them for real. No install, traced.","version":"1.0.0","publisher":{"kind":"domain","id":"rokha.ai","label":"rokha.ai","url":"https://rokha.ai"},"website":"https://rokha.ai","repository":"https://github.com/aetherBytes/rokha-sdk","remotes":[{"type":"streamable-http","url":"https://rokha.ai/mcp/jsonrpc"}],"packages":[],"published":"2026-09-25","updated":"2026-09-25","status":"online","auth":"","latency_ms":1167,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"hunt_report","title":"Hunt — a deep dive on any link","description":"A 402 purchase_required here is Rokha's own price for the call (the pack and your own x402 order), never the target site. Rokha's HUNT: give it one lead — a link (site, docs page, API or MCP endpoint, an x.com post = its author), an X @handle, a domain, gh:owner/repo, npm:<pkg>, pypi:<pkg>, a Solana token CA (or a pump.fun / DexScreener / Solscan link naming one), or a project name — and she crawl","read_only":true},{"name":"x_account_audit","title":"Audit an X account — is the following real?","description":"Rokha's account auditor: give it any X @handle and get an organic-ness audit — 0–100 score, ORGANIC/MIXED/SMOKE verdict, and the promotional-worth anchor in X-algorithm engagement units (reply 13.5 · quote 1.5 · repost 1.0 · like 0.5). Hard metrics from X's own numbers: engagement rate vs follower count, reply share (the hardest signal to buy), engagement variance across posts (bought engagement i","read_only":true},{"name":"send_agent_message","title":"Send Agent Message","description":"Send a message to a Rokha agent (default 'rokha-agent') and get its reply. With a logged-in identity (Authorization: Bearer <JWT>) the agent acts AS you — it can run your rigs (rig_run), read your saved keys/OAuth grants, and spend your budget; anonymous callers get general chat only. This is the door to have Rokha do work on your behalf over MCP.","read_only":false},{"name":"registry_search","title":"Search the Rokha Registry","description":"Search the public skill and MCP registries at once, plus what builders publish on Rokha (the live count is in GET /api/marketplace/registry/stats), by free-text query. Returns name, slug, provider, author, version, downloads, and description for each match. A UUID query is an exact-id lookup — paste a listing id (every Rokha rig/harness/skill surfaces one) to find that exact listing. Follow up wit","read_only":true},{"name":"registry_get_skill","title":"Get a skill's SKILL.md + install metadata","description":"Fetch everything an agent needs to adopt a Registry skill: the full SKILL.md (agentskills.io standard — frontmatter name/description + body), its classification (prompt-shaped vs scripted vs mcp), and required binaries. To install: save the returned skill_md as SKILL.md inside a folder named after the slug in your agent's skills directory.","read_only":true},{"name":"rig_search","title":"Find the rigs you own","description":"List YOUR saved rigs, newest first, optionally narrowed by `query` (matches the                  name/summary). This is how an agent RECOVERS: rig_author returns an id, but an                  agent that runs across sessions will not still be holding it, and without this it                  could only ever re-author from scratch — quietly making a second rig instead of                  finding the","read_only":true},{"name":"rig_get","title":"Read one rig in full","description":"Read ONE of your rigs in full — its steps, wiring, guards and stage. Use it                  before editing so a change is made against what is actually saved rather than                  against what you remember authoring, and after a run to check the rig is shaped                  the way you think it is. Owner-scoped. Requires Authorization: Bearer <JWT>.","read_only":true},{"name":"trace_search","title":"Read what a run actually did","description":"List your Traces — the durable record of what a run DID, newest first. This is                  the other half of rig_run: a run reports that it started, and the trace is where                  the answer lands. Without it an agent can run a rig and never learn whether it                  worked, which makes the run untestable. Filter by `rig_id` (this rig's runs),                  `parent_trace_i","read_only":true},{"name":"rig_run","title":"Run a saved Rig for real","description":"RUN a rig, for real, right now. Without this an outside agent could AUTHOR a rig,                  schedule it and hang a webhook on it — but never run one on demand, and so never                  test the thing it just built. Name the rig by `rig_id` (one you own or adopted) OR                  by `provider_id` + `external_id` (a published listing — this adopts YOUR OWN copy                  firs","read_only":false},{"name":"skill_author","title":"Author an Agent Skill (SKILL.md)","description":"Author a standard agentskills.io Agent Skill and get back its SKILL.md. A strong skill has: a `name` in kebab-case (lowercase letters, numbers, single hyphens, ≤64 chars); a `description` stating WHAT it does AND WHEN to use it, third person, with concrete trigger words (the field agents read to decide whether to load it); and `instructions` (the Markdown body), specific + imperative, ideally shap","read_only":false},{"name":"auth_resolve","title":"How do I authenticate with this MCP server?","description":"The AUTH LADDER: classify any MCP server URL — 'open' (no credential), 'key' (paste a token into the vault once), 'tier1' (one-click account-wide Connect for a known provider), or 'oauth_spec' (the MCP auth spec — connect directly, approve in a browser). Returns the one right next step. Works without login.","read_only":true},{"name":"rig_author","title":"Rig Author","description":"Author a multi-step Rig as a graph the runtime executes for real. `nodes` are the steps, `edges` {from, to, guard?} wire them; `structure_type` linear | dag (default) | stateful_graph (loops with guarded edges; an unfired guard skips its target). A step with no binding is a model turn with NO tools. A step that must do something is bound: `endpoint` + `tool` + `params` (a real MCP tools/call — you","read_only":false},{"name":"trace_get","title":"Trace Get","description":"READ one trace in full (input, result, status, timing) by `id`, or a whole run by `run_id`          (status, steps with their trace ids, output, every trace). Signed in (Authorization: Bearer          <token>): your own traces. No token: a PUBLIC rig's run is readable by anyone holding its          trace id or run id — the runner's identity is stripped. Anything else answers not-found.          RE","read_only":true},{"name":"registry_publish","title":"Publish a listing to the Rokha Registry","description":"Publish (or update) YOUR listing in the Rokha Registry so anyone — human or agent — can find and use it. Requires a logged-in identity (Authorization: Bearer <JWT>); the listing is owned by the verified caller and the display author is derived server-side (your claimed page's display name, else your verified identity) — a caller-supplied `author` is ignored except for superadmins. name must be keb","read_only":false},{"name":"auth_wallet_challenge","title":"Start wallet registration / login","description":"Step 1 of registering (or logging in) a user with a wallet keypair — no browser needed. Returns a challenge message to sign with the wallet's private key. Works for Solana (base58 Ed25519 address) and EVM (0x address). Follow with auth_wallet_verify. New wallets are auto-registered on first verify as a free account: 10 questions a day with Rokha, free listing, and 5 runs a day (model steps on your","read_only":false},{"name":"auth_wallet_verify","title":"Finish wallet registration / login → JWT","description":"Step 2: submit the signed challenge. On success returns session_token — a JWT to send as `Authorization: Bearer <token>` on every subsequent MCP/API request, unlocking the owner-scoped tools (page_claim, create_harness, rig_author, registry_publish, schedules, …). Solana: Ed25519 signature over the raw challenge message bytes (base58 or comma-separated bytes). EVM: EIP-191 personal_sign hex.","read_only":false},{"name":"studio_doors","title":"Studio Doors","description":"WHAT ROKHA COSTS. Rokha is the Agent Runtime and Marketplace — build tools, run them for real, sell or hire them. No platform payouts. THREE RUNGS: FREE, signed in (an agent signs in with a wallet over MCP) — 5 runs a day of tools on Rokha's runtime, model steps on your own key; PAY PER RUN — a run pack, 100 runs for $1 (x402, USDC, SOL or card); THE LAB ($29.99 a month, card, USDC or SOL) — full ","read_only":true},{"name":"market_search","title":"The Market","description":"THE MARKET (rokha.ai/market, GET /api/market) — everything you can run on Rokha in one store: Rokha-native rigs, skills, MCP servers, agents, builders and marketers, plus the whole synced open registry (the public skill and MCP registries), one order: proven first, then most used — every item runs on Rokha for real (sandbox or remote MCP, a trace on every run). Browse by `aisle` (what it is: all ·","read_only":true},{"name":"mark_check","title":"Mark Check — is this coin, account or link a punk?","description":"A 402 purchase_required here is Rokha's own price for the call (the pack and your own x402 order), never the target site. MARK CHECK — one deep read on any mark: a Solana contract address (or a pump.fun / DexScreener / Solscan / Birdeye link naming one), an X @handle or x.com link, or any public https link. A coin gets its mint + freeze authority and holder concentration (Solana RPC), the deepest ","read_only":true},{"name":"page_me","title":"My builder page (or claim suggestion)","description":"YOUR page as the logged-in identity sees it. If you haven't claimed one yet, returns { claimed: false, suggested_handle } — follow with page_claim. Carries your linked X account too: `x_handle` (the connected @handle), `x_verified_type` ('blue'/'business'/'government' or ''), `x_verified` (the derived bool) — all stamped by connecting X through the OAuth broker. Requires Authorization: Bearer <JWT","read_only":true},{"name":"page_claim","title":"Claim or update your public page","description":"Claim your public /@handle page (or update it — re-claiming your own handle edits in place; a new handle renames). The page is owned by the verified caller. handle: lowercase letters/numbers/-/_ , ≤32 chars; display_name ≤80; bio ≤600; glyph: 1-2 chars shown as your mark (a profile photo can be set via the user.profile.avatar harness); links: array of {label, url}; style: the page's BRAND knobs — ","read_only":false},{"name":"registry_adopt","title":"Adopt a published rig as your own runnable copy","description":"The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_search; the listing must carry a metadata.rig skeleton). Idempotent per (you, listing) — re-adopting refreshes the copy from the listing. Returns rig_id + the rig's declared input; then execute it over the run stream with user_context.rig_id and run_input. Run","read_only":false},{"name":"free_tier_status","title":"What the free tier includes","description":"THE FREE TIER — what anyone gets on Rokha each UTC day, read from the one definition the gates enforce. Free, no account: talk to Rokha (10 questions a day — the same taste signed in) and read everything public — the Market, every listing, public runs and traces, finished hunts and saved marks; no runs without an account (sign in free); no builds, hunts, marks or web searches without the Lab. Free","read_only":true},{"name":"agent_create","title":"Create your own agent","description":"Requires a JWT (sign in headlessly with auth_wallet_challenge → auth_wallet_verify). Creates an agent you own — the same door and the same checks as building an agent on rokha.ai: name + handle (lowercase letters, numbers, - and _, ≤32; reserved names and taken handles refused), optional tagline, persona (the voice it answers in — required to go live), greeting, glyph, avatar_url (https), accent, ","read_only":false},{"name":"product_get","title":"The price on a rig, skill, harness or agent","description":"Public. Is this item paid, and what does it cost? Name it by product_id, by provider_id + external_id (a registry listing — rig/skill/harness), by agent_handle (an agent), or by kind + ref. A pack is kind 'pack' + ref = the pack id. Returns {product:{id,title,model: one_time|monthly|per_run, price_cents, runs_per_pack, checkout_url}} or {free:true}; a priced item that also comes in a pack carries ","read_only":true},{"name":"product_checkout","title":"Buy access to a paid item","description":"Requires a JWT or an rk_ key. Buy product_id for YOURSELF. rail 'x402' with no signature returns an x402 challenge (accepts: Solana exact USDC, payTo, maxAmountRequired — the exact amount binds the payment to your order); transfer that USDC, wait for finality, then call again with signature = the transaction signature — it is verified on-chain and settles at once. rail 'usdc' + payer_wallet return","read_only":false},{"name":"purchases_mine","title":"What you have bought","description":"Requires a JWT or an rk_ key. Your paid unlocks, passes (period_end) and run packs (runs_left).","read_only":false},{"name":"subscribe","title":"Start your own Lab month","description":"Requires a JWT or an rk_ key (sign in headlessly with auth_wallet_challenge → auth_wallet_verify). Starts the Lab month — $29.99 a month, full access to everything: the runtime, the Lab, 300 runs a day (model steps on your own model key) — for YOURSELF; it never names another account. rail 'usdc' + payer_wallet returns exact pay instructions (send EXACTLY that USDC from payer_wallet; it confirms o","read_only":false},{"name":"subscription_status","title":"Your Lab access and your runs","description":"Requires a JWT or an rk_ key. Read-only. Do I have the Lab, and what is left today: lab {has_lab, runs_per_day, runs_used_today, runs_left_today, schedules_cap, schedules_used, fastest_cadence}; your access: studio (true = full access), access (rent | holder | house | none …), current_period_end, tier, full_access; and the ladder — free runs a day, the run pack (product_id, price, how to buy) and ","read_only":true},{"name":"tools_catalog","title":"Find any Rokha tool","description":"tools/list carries the `core` set only; this finds the rest, and every tool is callable whether or not it is listed. No arguments: the toolsets with counts. `query`: words matched against every tool's name, title and description — one line per hit (name · title · toolset). `toolset`: one set in full (build · agents · sell · lab · signet · tasks · about). `name`: one tool's complete definition, inp","read_only":true}],"server_info":{"name":"rokha","title":"Rokha — the Agent Runtime and Marketplace","version":"1.0.0"},"category":"web-search","tags":["agents","crypto","ecommerce"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-25","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/ai-rokha-rokha/"}