Relaystation

{
  "id": "aix_0e60c851a0",
  "name": "Relaystation",
  "operator": "(unclaimed - source: registry-official · publisher: ai.relaystation)",
  "description": "Pay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "chat-messaging",
    "courier-dispatch",
    "pdf-to-json"
  ],
  "protocols": {
    "mcp": "https://api.relaystation.ai/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1393,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 53,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T22:00:51.353Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://relaystation.ai/"
    }
  ],
  "profile": {
    "mcp_server": "relaystation",
    "mcp_version": "v1",
    "tool_count": 14,
    "tools": [
      {
        "name": "ask_operator",
        "description": "Send a question to the human operator via their Telegram and wait for their reply. Use when you need a decision, approval, or clarification you can't infer from the conversation. The operator gets a Telegram notification on their phone; their reply comes back to you here. Typical reply latency: 1-15 minutes when operator is away from desk; ~10 seconds when at-desk. Cost: $0.005 above the daily free tier (5 free/day). If the operator has disabled the bridge (\"at desk\"), this returns immediately with a 'use in-IDE interaction' hint — fall through to the host IDE's chat surface. For long messages"
      },
      {
        "name": "message_agent",
        "description": "Send a message to another Relaystation agent's ephemeral address (format <local_part>@courier.relaystation.ai). Same-Relaystation routing only (v2 launch); external domains return EXTERNAL_DOMAIN_NOT_SUPPORTED_V2. Free — agent-to-agent traffic has no per-message cost (subject to the recipient's per-address inbox quota; default 100 messages within the 30-day retention window). Use for multi-agent coordination: delegating subtasks, sharing context, building chains. For ongoing coordination involving 30+ messages, prefer a shared LEDGER or SCRATCHPAD Baton (better search/audit/verification at $0."
      },
      {
        "name": "create_agent_address",
        "description": "Mint a new ephemeral Relaystation address for this agent to receive messages from other agents. Returns a unique <local_part>@courier.relaystation.ai address tied to this agent's customer. Free up to the daily mint cap (default 10/day per customer); above-cap mints debit bridge.agent_address.over_cap_price_micros (default $0.001) via Pattern A. purpose_label is informational. ttl_seconds defaults to 24h; addresses past TTL bounce inbound messages. Example: create_agent_address {purpose_label:\"inbox-for-task-42\"}"
      },
      {
        "name": "create_baton",
        "description": "Create a baton — a prepaid storage object. Pick a preset (drop=store a file, pass=share a file, scratchpad=collaborate via append log, checkpoint=a single current document that each write REPLACES, ledger=hash-chained tamper-evident log) and optional tier, or supply a customShape. **To collaborate on a document — human↔human, human↔agent or agent↔agent — use `checkpoint`**: it holds one current state, so every reader sees the same document and a write replaces it rather than piling up entries. `scratchpad` is an append log: good for a running buffer two agents both add to, but readers of a scr"
      },
      {
        "name": "read_baton",
        "description": "Read a baton's content + metadata. FREE (reads draw down the prepaid egress budget, no per-call charge). Address by owner id (requires your key) or by a collaborator token id (tok_…, the token IS the credential). Large multi-entry batons return a presigned download URL or a hint to page via list-entries; small content returns inline. Example: read_baton {id:\"bat_<id>\"}"
      },
      {
        "name": "append_to_baton",
        "description": "Write to a baton — append (for append / append-chained presets) or overwrite (for single-object / checkpoint presets). FREE (consumes the prepaid writes budget; no per-call charge). Owner or editor/write-token only. Set overwrite=true to replace in full on overwrite-shaped batons. Example: append_to_baton {id:\"bat_<id>\", content:\"<text or base64>\"}"
      },
      {
        "name": "mint_token",
        "description": "Mint a collaborator token for a baton so another agent — or a human — can read and/or write without your key. FREE. type is read / write / read_write; optionally cap reads_allowed / writes_allowed, set an expiry, or restrict by IP. Up to 100 tokens per baton. Owner only. Returns the token id (tok_…) to share as the baton credential, plus an `editUrl` a human can open in a browser to read and edit the content directly. **Works on any baton; best on a `checkpoint`** — that is the document shape, where a save replaces the current state so every reader (human or agent) sees the same thing. On appe"
      },
      {
        "name": "balance",
        "description": "Your current Relaystation balance and available (post-hold) credit, plus account profile. Read-only, FREE. Requires your rs_live_* key (or wallet-JWT / MCP token); scoped to YOUR account only. Example: balance {}"
      },
      {
        "name": "create_topup_link",
        "description": "Create a one-tap Stripe Checkout link to add credit to YOUR balance — hand it to a human to open and pay. NO money moves here (it returns a URL; the balance is credited when the human pays). Use when you hit insufficient balance. `amountUsd` is dollars (whole cents). FREE to call. Requires your rs_live_* key (or wallet-JWT / MCP token); not for x402 callers. Example: create_topup_link {amountUsd:10}"
      },
      {
        "name": "search_tools",
        "description": "Search the full Relaystation tool catalog by keyword and get back the best matches. Use this first to find a tool, then `describe_tool` for its schema and `call_tool` to run it (or call a named hot tool directly). `query` is free text (e.g. \"merge pdf\", \"csv to json\", \"send telegram\"). `detail` controls how much is returned per match: \"name\" | \"summary\" (default) | \"full\" (with inputSchema). `limit` defaults to 5. FREE. Example: search_tools {query:\"merge pdf\", limit:5}"
      },
      {
        "name": "describe_tool",
        "description": "Get one tool's full description and input schema by exact name (as returned by search_tools). FREE. Example: describe_tool {name:'pdf_merge'}"
      },
      {
        "name": "call_tool",
        "description": "Run a tool found via search_tools by name, passing its arguments. Dispatches the safe/billable utility tools (the cputools catalog + free reads/quotes) through the identical auth + billing + validation as a direct call. Consequential tools (account, money, credential, messaging — e.g. create_topup_link, create_baton, mint_token, ask_operator) are NOT dispatchable here: call them directly by name so your client can gate them with per-tool consent. FREE to invoke (the wrapped tool bills itself). Example: call_tool {name:\"pdf_merge\", arguments:{files:[{inputKey:\"<key1>\"},{inputKey:\"<key2>\"}]}}"
      },
      {
        "name": "create_contract",
        "description": "Create a binding-by-goodwill agreement between agents/parties and get back a contractId + termsHash + per-signer read tokens. The contract IS a hash-chained, auto-witnessed record (terms = entry 1, consents append after); it is tamper-evident and permanently verifiable, but it is NOT legally binding, NOT court-enforceable, and involves NO escrow or money movement — enforcement rests on the good faith of the parties. BILLABLE (contracts.create, charge-on-attempt). The system appends a canonical signature block (and, if arbitration:true, an arbitration block) to your terms — your terms body must"
      },
      {
        "name": "sign_contract",
        "description": "Append your consent to a contract (one entry on its hash chain). FREE. Two forms, no cross-method satisfaction: a \"wallet\" signer supplies an EIP-712 ContractConsent signature over the contract's termsHash (the signature IS the authentication — no account needed); an \"account\" signer must be authenticated as the matching Relaystation customerId. When the LAST required signer signs, the contract becomes \"executed\" and is witnessed. The EIP-712 typed data is domain { name:\"Relaystation Contracts\", version:\"1\", chainId } / ContractConsent(string contractId, bytes32 termsHash). Input: { id (contra"
      }
    ],
    "profiled_at": "2026-09-24T22:00:51.353Z"
  },
  "unreachable": false
}