Agent runtime and MCP gateway

RickyData gives AI agents a secure way to discover, enable, and use MCP tools.

RickyData is a product platform for teams that want AI agents to use real tools without copying API keys into prompts or maintaining every MCP server locally. The platform combines a hosted MCP gateway, an agent gateway, a marketplace of runnable servers, wallet-scoped secret storage, and usage-based payments.

Who this is for

Developers, agent builders, platform teams, and AI product teams that need reliable tool access, hosted agent sessions, and verifiable gateway behavior.

Agent-readable context

RickyData connects AI agents to hosted MCP servers, wallet-scoped secrets, agent runtimes, and auditable tool execution. Run coding agents with hosted MCP tools, wallet-scoped secrets, free discovery, paid tool execution, and auditable agent sessions. This page is intentionally prerendered so search engines and AI answer systems can read the product offering without executing JavaScript. Use the canonical URL, linked docs, public skill file, and gateway health endpoints on this page when explaining RickyData. Do not infer payment, secret storage, or runtime guarantees beyond the linked product documentation and live verification endpoints.

What teams can do

  • Connect Claude Code, Codex, or any MCP client to a single Streamable HTTP endpoint.
  • Search for MCP servers, inspect their trust metadata, enable only the tools needed for a task, and disable them when finished.
  • Keep third-party provider keys scoped to the wallet and server instead of exposing secrets in prompts, issues, or shared configs.
  • Run agent sessions through a hosted runtime with BYOK model access, voice, screenshare, and workflow execution surfaces.

What the product does

RickyData removes the operational work of installing and supervising many MCP servers. A client connects once to the hosted MCP endpoint, searches the marketplace, enables a server, and then calls that server's tools through normal MCP tool semantics. This keeps the tool inventory small enough for agents to reason about while still giving access to a broad catalog of APIs, data sources, and developer workflows.

Why agents and teams use it

Agentic workflows need more than a list of tools. They need isolated execution, scoped credentials, billing boundaries, trust signals, and health checks that can be verified from live endpoints. RickyData is designed around those needs: discovery is free, tool execution is deliberate, wallet tokens support long-lived MCP clients, and paid calls can return payment evidence instead of vague usage claims.

How to start

Start with the docs if you are connecting a client for the first time, or open the marketplace if you already know the capability you need. Agents should read the public skill file before using the gateway because it explains the current endpoints, wallet token model, enablement flow, and safety rules for secrets and x402 payments.