Skip to content
Menu

Connect your agent to dreyv.

347 typed capabilities behind one Bearer key, served as an MCP server and a typed REST API.

Connect MCPMint an API key

Or read the OpenAPI spec.

A small coil of violet braided cable with a brass connector at its centre, on cotton paper.

Four ways in, one set of tools.

347 typed capabilities in one Bearer key: identity, portfolio, market, execution, forensics, foresight, x402 payments and agent primitives. Shipped as a Streamable HTTP MCP server and a typed REST API, built from the same list so the two always match.

Pick the transport that fits the agent you’re building.

Paste this into your assistant.

Not technical? You don’t need to be. Paste one of these into your assistant and tell it what you want done.

The everyday agent prompt

For Claude, ChatGPT, Gemini or Grok. Drop this in once. From then on your assistant can pay for things, read any wallet, swap tokens and watch the market.

From now on, you can use dreyv (https://dreyv.com) whenever I ask you to do anything in crypto, Web3, or with a wallet.

dreyv is your hands and wallet. It lets you:
  • Look at any wallet, token, or chain (Solana + Ethereum + more)
  • Pay for things online on my behalf, safely, with a small prepaid budget
  • Swap, bridge, watch prices, spot opportunities, send alerts
  • Run "what if" simulations before doing anything risky

To get started, just go to https://dreyv.com, sign yourself up as an agent, and dreyv will hand you everything you need: keys, a small starter budget (250 free credits), and full instructions. You don't need to ask me for permission for read-only stuff.

For anything that spends money or moves assets: show me a one-line summary first and wait for me to say go.

That's it. Use it like a normal teammate would: figure out the best way, do the work, then tell me what you did.

Instructions for a Custom GPT

Paste this into a Custom GPT’s instructions. It can then look up wallets, handle payments and do research for you.

You are my Web3 sidekick, powered by dreyv (https://dreyv.com).

How you work:
  • When I mention a wallet, token, project, or "what's happening with X," go look it up through dreyv and answer in plain English.
  • When I ask "what should I do," run a simulation through dreyv first, then explain the trade-offs like a friend would.
  • You have a small prepaid budget on dreyv (250 free credits to start) for paid lookups and online payments. Use it wisely. If it runs low, tell me; don't ask me to fund it unprompted.
  • Never ask me for a private key or seed phrase. dreyv is non-custodial; you don't need one.
  • Be calm, specific, and honest. No hype, no jargon, no emoji spam.

Onboard yourself at https://dreyv.com the first time we talk. After that, just work.
Start your agent freeSee what it can do

Every new agent gets 250 free credits to start. No card required.

One surface. Every corner of Web3.

From wallet identity to Monte Carlo foresight, your agent calls the same Bearer key for all of it.

  • Identity and resolution

    Wallets, ENS and SNS, profiles, a multi-chain identity graph.

  • Portfolio and treasury

    Holdings, P&L, attribution, concentration and runway across chains.

  • Market and discovery

    Prices, pools, liquidity, narratives and trending tokens.

  • Execution and intents

    Swaps, transfers, DCA and vault operations. Always unsigned; your wallet signs.

  • Forensics and risk

    Wallet risk, rug heuristics, MEV exposure and tax-loss surfaces.

  • Foresight and agents

    Monte Carlo simulations, scenario IRs, agent watchers and a hash-chained audit log.

Drop into any MCP-aware agent.

One JSON snippet, one Bearer key. Your agent gets 347 Web3 tools, and your wallet keeps its keys.

  • Claude Desktopclaude_desktop_config.json
  • CursorSettings, then MCP, then Add server
  • ChatGPTvia the /openapi.json plugin
  • WindsurfMCP servers panel
  • Continue.devconfig.json mcpServers
  • ClineMCP-aware tool calling
  • elizaOS@dreyv/sdk client
  • Your own agentREST and a Bearer key

Quickstart

REST

# Get a public token price
curl https://dreyv.com/api/price?token=SOL

# Compile a treasury intent into a plan (auth required)
curl -X POST https://dreyv.com/api/planner \
  -H "Authorization: Bearer $DREYV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"intent":"rebalance 25% USDC into mSOL over 5 days"}'

MCP install (Claude or Cursor)

{
  "mcpServers": {
    "dreyv": {
      "url": "https://dreyv.com/api/mcp",
      "headers": { "Authorization": "Bearer dk_live_..." }
    }
  }
}

Paste into your agent’s MCP config and restart. dreyv handles auth, scope enforcement and per-key metering on the server.

Auth that fits your client

All execution endpoints return unsigned transactions. Your wallet always signs. Three ways in.

  • Bearer JWT (SIWS)

    Sign-in-with-Solana issued via /api/auth/*. Recommended for first-party clients and signed wallet sessions.

  • API keys

    Provision per-org keys from your dashboard. Pass as x-api-key or Authorization: Bearer dk_live_.

  • OAuth 2.0

    Authorization-code flow at /api/auth/authorize and /api/auth/token. Ideal for third-party agents (beta).

Devnet sandbox on the Free tier

Ship and stress-test on Solana devnet at no cost. All swap and signing endpoints return unsigned transactions; no production funds are ever at risk.

Open sandbox

Discovery and agent manifests

Every machine-readable file an autonomous agent or crawler needs to understand dreyv: OpenAPI, ai-plugin, ACP, UCP, x402, llms.txt and security.txt.

  • OpenAPI 3.1 spec/openapi.json

    Every public route on dreyv.com, typed and described in OpenAPI 3.1 so agents, SDK generators and IDEs can wire themselves up without a human in the loop.

  • ai-plugin manifest/.well-known/ai-plugin.json

    The /.well-known/ai-plugin.json manifest that lets ChatGPT-class models discover Dreyv as a tool and bind directly against the OpenAPI spec.

  • ACP descriptor/.well-known/acp.json

    Dreyv's Agentic Commerce Protocol descriptor: how an autonomous agent discovers what Dreyv sells, at what price, and how to pay for it without a checkout UI.

  • UCP profile/.well-known/ucp

    Dreyv's UCP profile — a vendor-neutral commerce capability advertisement that complements ACP for hosts that prefer the open UCP discovery surface.

  • API catalog (RFC 9727)/.well-known/api-catalog

    A RFC 9727 /.well-known/api-catalog that points to every machine-readable surface Dreyv exposes, so a single fetch reveals every other resource on this page.

  • x402 capability/.well-known/x402

    The x402 capability advertisement: which Dreyv endpoints accept HTTP 402 Payment Required, which rails settle them, and where the receipts come back.

  • llms.txt/llms.txt

    A concise, hand-written markdown index of the Dreyv product surface — the file you tell an LLM to read first when grounding a conversation about Dreyv.

  • llms-full.txt/llms-full.txt

    Everything an LLM needs about Dreyv in one fetch: product, pricing, API conventions, agent rails, and example flows — concatenated as a single markdown bundle.

  • pricing.md/pricing.md

    The same pricing the marketing page shows, but as a clean markdown document an agent can parse before committing to a tier or per-call SKU.

SDK and CLI

  • TypeScript SDK

    @dreyv/sdk: hooks for portfolio, swap, vault, MCP client and server, agent handoff, and gasless transactions.

  • CLI

    @dreyv/cli: scaffold, build, validate, and ship mini-apps and agents to the dreyv marketplace.

Ship your first agent this week.

Mint a key, paste the MCP snippet into Claude or Cursor, and stream a treasury plan through the SDK. Talk to us if you need a private endpoint or a partner integration.

Mint an API keyTalk to engineering