Robyn — Gasless Cross-Chain for AI Agents

Official registry AI and agents

Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http robyn-gasless-cross-chain-for-ai-agents 'https://api.anygas.xyz/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "robyn-gasless-cross-chain-for-ai-agents": {
            "type": "http",
            "url": "https://api.anygas.xyz/mcp"
        }
    }
}
NPM package anygas-mcp
Claude Code
claude mcp add robyn-gasless-cross-chain-for-ai-agents -e 'ROBYN_SVC=<ROBYN_SVC>' -e 'ROBYN_SIGNER_KEY=<your robyn_signer_key>' -- npx -y anygas-mcp@1.0.2
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "robyn-gasless-cross-chain-for-ai-agents": {
            "command": "npx",
            "args": [
                "-y",
                "anygas-mcp@1.0.2"
            ],
            "env": {
                "ROBYN_SVC": "<ROBYN_SVC>",
                "ROBYN_SIGNER_KEY": "<your robyn_signer_key>"
            }
        }
    }
}

Environment variables

  • ROBYN_SVC Base URL of the Robyn gateway (gasless quote/route/execute API). Optional — defaults to https://api.anygas.xyz/svc.
  • ROBYN_SIGNER_KEY secret Optional hex private key. If set, the server signs and submits gasless intents autonomously; if omitted, it returns unsigned intents for the agent/user to sign.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Robyn — AnyGas
  2. What Robyn does
  3. The mesh — 22 EVM chains + Stellar
  4. Proof — real mainnet transactions
  5. Integrate three ways
  6. Fees
  7. One-time setup
  8. Integrate, don't replicate
  9. Repo layout
  10. Docs
  11. License

Robyn — AnyGas

A gasless intent layer for AI agents. Sign one intent, hold no native gas anywhere, and pay or move value across 22 EVM chains + Stellar mainnet. Robyn's relayer fronts the gas — on the source chain, the destination chain, and the bridge — and is reimbursed from the token being moved. The agent's signer needs zero native balance. It only signs.

🔗 Live now — anygas.xyz · Ask the concierge · Live mesh (JSON) · llms.txt

npx jsr add @robyn/agent-kit
import { RobynAgent } from '@robyn/agent-kit';

const agent = new RobynAgent({ signer, svc: 'https://api.anygas.xyz/svc' });

// Move value across chains — one signature, zero gas on either side.
const { id } = await agent.crossChain({
  fromChain: 8453,  fromToken: USDC_BASE,   // Base
  toChain:   42161, toToken:   USDC_ARB,    // Arbitrum
  amount:    25_000000n,
});

That's the whole thing. No faucet, no per-chain gas top-ups, no bridge picking, no native token held anywhere. The signer signs a single Permit2 intent; Robyn does the rest and takes its fee in the token being moved.


What Robyn does

Two capabilities, one gasless model:

  • Gasless pay — transfer or pay in any verified token on any supported chain. The relayer fronts gas and is repaid from the token (fee auto-converted to a verified asset when needed). See pay / payAny / buy.
  • One-signature cross-chain — move value between any two supported chains (including to and from Stellar) with a single Permit2 signature and zero gas on either side. See route (quote) / crossChain (execute) / routeStatus (track).

Live on mainnet, both directions to Stellar.

The mesh — 22 EVM chains + Stellar

A single relayer mesh spans 22 EVM chains and Stellar mainnet. Any node can be a source or a destination — EVM↔EVM and EVM↔Stellar both run on mainnet today. Stellar is a first-class destination: set toChain: "stellar", toToken: "USDC".

Query the live registry and route graph at runtime — agent.chains() / agent.routeInfo(), or the robyn_mesh tool.

Proof — real mainnet transactions

Robyn is live. These are on-chain, verifiable moves — not testnet, not simulated:

WhatTransaction
EVM→EVM Permit2 delivery (Base→Arbitrum)0x98a988b1…
EVM→Stellar (source leg, Arbitrum)0x22c16ca8…
EVM→Stellar (destination leg, Stellar)63f5eb1c…
Gasless pay_any on Stellar mainnetd96d7e52…

Stellar mainnet contract: CDDJAVK2CLA2LIYJWXH4APVFEDQBH3HT72UFAVSLNBLDTEZELJ6PEKD2

Integrate three ways

Pick the surface that fits your stack. All three are MIT client packages published on JSR.

1. SDK — @robyn/agent-kit

The one-import way for an agent (or any automated system) to transact gaslessly.

npx jsr add @robyn/agent-kit
import { RobynAgent } from '@robyn/agent-kit';
const agent = new RobynAgent({ signer, svc });
await agent.payAny({ token: ANY, to: merchant, amount, verifiedAsset: USDG }); // gasless pay
await agent.crossChain({ fromChain: 8453, fromToken, amount, toChain: 42161, toToken }); // cross-chain
2. MCP server — @robyn/mcp

Give any MCP-capable agent (Claude Desktop, Cursor, agent frameworks) Robyn's tools directly.

npx jsr add @robyn/mcp
{
  "mcpServers": {
    "robyn": {
      "command": "npx",
      "args": ["-y", "robyn-mcp"],
      "env": {
        "ROBYN_SVC": "https://api.anygas.xyz/svc",
        "ROBYN_SIGNER_KEY": "0x…"   // optional — omit for a safe read-only server
      }
    }
  }
}

Tools: robyn_mesh, robyn_quote, robyn_route_status (no credentials) and robyn_cross_chain (needs a signer key).

3. Framework adapters — @robyn/adapters

The same four tools as a drop-in for the agent framework you already use.

npx jsr add @robyn/adapters
import { robynTools }          from '@robyn/adapters/ai-sdk';    // Vercel AI SDK
import { robynLangchainTools } from '@robyn/adapters/langchain'; // LangChain
import { robynActionProvider } from '@robyn/adapters/agentkit';  // Coinbase AgentKit
import { robynOpenAITools, robynAnthropicTools, robynDispatcher } from '@robyn/adapters/schemas'; // raw function-calling

Fees

  • Gasless pay — the actual gas cost plus a small margin of ~5% of gas, charged in-token.
  • Cross-chain — 0.25% of the moved amount, charged in-token.

Always paid from the token you're already moving — the agent never needs a native balance to cover fees. Every quote returns the fee before you execute (route / robyn_quote).

One-time setup

Cross-chain uses Permit2 SignatureTransfer. Once per (token, chain), the signer approves Permit2 to spend the token — a standard, single ERC-20 approval:

await token.approve('0x000000000022D473030F116dDEE9F6B43aC78BA3', ethers.MaxUint256);

After that, every move is a single gasless signature — no native token, ever.

Integrate, don't replicate

These packages are MIT — build on Robyn, ship it, and sell your product built with it, no restrictions. The license covers only these client libraries. Robyn's relayer, smart contracts, and network are proprietary and are not licensed here; don't use these packages (or the Robyn API) to run a competing gasless-relay service or to replicate Robyn. See NOTICE.

Build with Robyn: yes. Clone Robyn to cut it out: no.

Repo layout

packages/agent-kit/   @robyn/agent-kit — the SDK
packages/mcp/         @robyn/mcp — the MCP server
packages/adapters/    @robyn/adapters — framework adapters
docs/                 integration guide, fee & security overview

Docs

License

MIT for the client packages in this repo. See NOTICE for scope.

Frequently asked questions

What is Robyn — Gasless Cross-Chain for AI Agents?

Gasless cross-chain for AI agents: 25 nodes incl. Solana & native Bitcoin. One signature, no gas.

How do I install Robyn — Gasless Cross-Chain for AI Agents?

It runs as a remote server. In Claude Code: claude mcp add --transport http robyn-gasless-cross-chain-for-ai-agents 'https://api.anygas.xyz/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Robyn — Gasless Cross-Chain for AI Agents need an API key?

Yes. It expects ROBYN_SIGNER_KEY, which you set in its configuration.

Is Robyn — Gasless Cross-Chain for AI Agents open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Robyn — Gasless Cross-Chain for AI Agents?

It is published by ox31461. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.