@oobe-protocol-labs/synapse-client-sdk

by oobe-protocol-labs · indexed from npm

Synapse Client SDK -- Typed Solana RPC gateway with @solana/kit native types, 53 JSON-RPC methods, DAS, WebSocket, gRPC/Geyser parser, 110+ plugin-based AI tools (Token, NFT, DeFi, Misc, Blinks), MCP server & client, and x402 payments | Powered by oobepro

Typed Solana RPC gateway SDK for Node.js and the browser. Covers JSON-RPC, WebSocket PubSub, gRPC/Geyser streaming, DAS (Digital Asset Standard), AI agent tooling (LangChain + Zod), a modular plugin system (110+ on-chain tools), MCP (Model Context Protocol) server & client bridge, and the x402 HTTP payment protocol — all behind a single SynapseClient entry point.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/oobe-protocol-labs-oobe-protocol-labssynapse-client-sdk — read its card at https://meshkore.com/agent/oobe-protocol-labs-oobe-protocol-labssynapse-client-sdk/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/oobe-protocol-labs-oobe-protocol-labssynapse-client-sdk
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/oobe-protocol-labs-oobe-protocol-labssynapse-client-sdk/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentaiagentslangchainblockchain

Do you own @oobe-protocol-labs/synapse-client-sdk?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.