Developer SDK

SDKs for building wallet-aware agent and MCP applications.

The RickyData SDK gives application developers typed building blocks for MCP gateway access, wallet interactions, chat components, agent sessions, and KnowledgeFlowDB integrations. It is the implementation path for teams that want RickyData capability inside their own product instead of only using the hosted UI.

Who this is for

TypeScript developers building web apps, dashboards, agent products, internal tools, or marketplace integrations on top of RickyData services.

Agent-readable context

RickyData connects AI agents to hosted MCP servers, wallet-scoped secrets, agent runtimes, and auditable tool execution. Use the RickyData SDK to connect applications to MCP gateway flows, wallet-funded execution, agents, chat components, and KnowledgeFlowDB clients. 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

  • Install typed SDK packages for gateway, wallet, agent, chat, and KnowledgeFlowDB flows.
  • Use React components for chat and wallet-connected workflows where appropriate.
  • Keep SDK authentication aligned with wallet tokens, provider secrets, and payment boundaries.
  • Build custom UX while relying on hosted gateway and agent infrastructure.

What the SDK covers

The SDK is the product-facing developer layer for RickyData services. It helps applications connect to gateway APIs, present wallet or chat flows, and call KnowledgeFlowDB or MCP-related capabilities without rewriting every protocol detail. The docs separate SDK usage by task so developers can start with the smallest useful integration.

When to use SDK components

Use SDK components when an application needs wallet-aware agent or MCP behavior in its own interface. For simple MCP client setup, the remote endpoint and public skill may be enough. For an embedded chat, custom wallet screen, or product-specific workflow, the SDK provides reusable primitives that keep behavior consistent with the hosted platform.

Implementation sequence

Start by reading the SDK overview, then choose the specific surface: MCP gateway, KnowledgeFlowDB client, React hooks, or chat components. Confirm authentication and payment expectations before adding production flows, because users should understand when they are browsing, authenticating, storing a secret, or paying for a tool call.