MCP Radar
MCP-Server

Robyn — Gasless Cross-Chain for AI Agents

io.github.ox31461/robyn
Krypto & Web3 Payments & Fintech Sicherheit Öffentlich und erreichbar MCP 2025-11-25

Was dieses MCP kann

Supports gasless cross-chain transfers, wallet and transaction checks, spending mandates, privacy-preserving messaging, and signed transfer evidence.

Funktionen

Tools

87 Tools
null_agent_guide
NULL — the complete agent handbook (do everything, correctly)
One read that teaches an agent to use every NULL capability with the right privacy posture: create an identity, seal + send + scan, start forward-secret sessions, drop an anonymous tip, check a Legacy heartbeat, make/detect stealth payments, and what each action reveals to whom. All crypto is local (SDK at /svc/msg2-sdk.mjs; browser bundle /svc/anygas-web.js); this MCP only relays sealed/signed material. Read-only, static knowledge.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_balance
NULL Pay — IP-blind balance read
Reads an address balance through the NULL server-side RPC proxy, so YOUR IP never reaches any public RPC provider (this host queries upstream from its own address). BE HONEST ABOUT THE TRADE: querying a stealth address you derived LINKS that address, your session, and the time of interest AT THIS RELAY — exactly the linkage stealth addressing hides from everyone else. Nothing reaches the RPC about you, but if relay-side unlinkability matters, batch several addresses (including decoys) in one sitting rather than polling one address on a schedule. Chains: Base + Arbitrum (unified). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address'], 'properties': {'address': {'type': 'string', 'description': '0x address (e.g. a derived stealth payment address)'}}, 'additionalProperties': False}
null_calls_info
NULL Calls - capabilities of the IP-blind voice/video relay
What the blind call relay offers (1:1 and conference, codecs, join-token model). Media keys are sealed through the feed and never reach the relay. Calls themselves need a media-capable client (browser); agents can read the posture and hand a human the join flow.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_capsule_cancel
NULL Lifeline - cancel an UNRELEASED time capsule ("I am safe") (lane)
Destroys a future-dated capsule you sent with {holdMs, cancellable:true}, using its one-time cancel token. Already-released rows are untouchable. The token proves nothing about who you are. Private-lane-only: use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['token'], 'properties': {'token': {'type': 'string', 'description': 'the one-time cancel token returned when the capsule was sent (20-64 url-safe chars)'}}, 'additionalProperties': False}
null_ecosystem
NULL — discover the whole ecosystem in one call
The live NULL manifest: every product (messenger, Pay, Vault, Drop, Legacy, Agent Wire, forward secrecy), its status, its page, the wired/proposed integrations between them, the security spine, and the concept pipeline. This is the same single source of truth the owner console and the human Suite read — a new product that ships appears here automatically. Pair it with null_agent_guide for the how-to. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_login_verify
Sign in with NULL - verify an assertion (for agents that ARE the relying party)
Stateless dual-signature check (secp256k1 + ML-DSA-65) of a NULLAUTH1 assertion for YOUR rp domain and the ONE-TIME challenge YOU issued; returns {ok, psid, mode, named, meta, handle(claim)}. Prefer verifying locally with @null/login-rp (no call at all); this tool is the convenience path. rp + challenge are mandatory - without them cross-site replays would verify. A named handle is a CLAIM until checked against the published record. Public on every lane.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['assertion', 'rp', 'challenge'], 'properties': {'rp': {'type': 'string', 'description': 'your domain, e.g. example.com'}, 'assertion': {'type': 'string', 'description': 'NULLAUTH1.<base64>'}, 'challenge': {'type': 'string', 'description': 'the single-use challenge you issued (>=16 chars)'}}, 'additionalProperties': False}
null_market_delist
NULL Agent Market - remove a listing (relay of a FRESH delist card)
Relays a fresh (<10 min) self-issued card whose claim is {purpose:"delist"} - a public listing card can never be replayed to delist someone. A market moderator adds modCred (a role credential {kind:role, ctx:market, role:moderate} from the operator root) and claim.target to remove another listing.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['card'], 'properties': {'card': {'type': 'string'}, 'modCred': {'type': 'string'}}, 'additionalProperties': False}
null_market_list
NULL Agent Market - list an agent (relay of a card you SIGNED locally)
Relays a NULLCRED1 card the agent issued ABOUT ITSELF (subject = issuer = its own meta; SDK credentialIssue, or the stdio door null_market_list_me which mints it for you). One listing per identity, 30 days, re-post to refresh. Past half-full a NEW listing needs one Plus pass (pass). Note: this door sees your IP next to a public card that names you - the stdio door (npx anygas-mcp) submits over the relay, IP-blind.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['card'], 'properties': {'card': {'type': 'string', 'description': 'NULLCRED1.<...> self-issued card'}, 'pass': {'description': 'a Plus pass, only when the market is over half full'}}, 'additionalProperties': False}
null_market_listings
NULL Agent Market - the public listing set (verify each card yourself)
Every current listing {card, at}; identical for every reader. The registry checked only the classical half of each card when it was listed, so it is never a trust oracle: verify the FULL dual signature of any card you rely on (SDK credentialVerify, or the stdio door null_market_browse which verifies them all). Listings age out after 30 days.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_names_market
NULL Names - the secondary market (signed listings + how to buy/sell/transfer)
Live listings of premium handles for sale, plus the full deal protocol: agree peer-to-peer in a sealed chat, pay stealth or via NULL Escrow 2-of-3, then finalize with the dual-signed (secp + ML-DSA) witness-chained transfer and a 2% ($1 min) fee receipt. Listing your own handle: sign null-name-list/v1|name|priceUsd|ts with your identity spend key and POST /api/nullnames/list.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_names_quote
NULL Names - price any handle (ENS-seeded, 7+ chars free forever)
Quotes a handle: 3ch $512/yr, 4ch $128/yr, 5-6ch $4/yr (deliberately under ENS), 7+ characters FREE forever. Includes live state (available/registered/grace/premium with the 21-day Dutch decay) and the exact register->pay->claim steps. Names are public by definition - quoting one reveals nothing.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': '3-32 chars, leading alphanumeric'}}, 'additionalProperties': False}
null_notarize
NULL Notary - prove a document existed, without revealing it (lane)
Proof-of-existence: hash the document LOCALLY (sha256, 64 hex) and send only the hash. The issuer countersigns {h, ts} with ML-DSA-65 (post-quantum); ts is SERVER-assigned. Optional owner endorsement: ownerAddr + ownerSig = EIP-191 over "null-notary/owner/v1|<h>"; if you add ownerMeta and that identity publishes a PQ key, ownerSig2 (ML-DSA over the same string) is REQUIRED. Proves existence-by-time (+ endorsement), never authorship or uniqueness. Verify with null_prov_issuer (pin the key) + SDK notaryVerify. Private-lane-only: use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['h'], 'properties': {'h': {'type': 'string', 'description': 'sha256 of the document, 64 lowercase hex - NEVER the content'}, 'ownerSig': {'type': 'string', 'description': 'EIP-191 sig over null-notary/owner/v1|<h>'}, 'ownerAddr': {'type': 'string', 'description': '0x address endorsing the hash'}, 'ownerMeta': {'type': 'string', 'description': 'st:eth:0x... of the endorsing identity'}, 'ownerSig2': {'type': 'string', 'description': 'base64 ML-DSA-65 over null-notary/owner/v1|<h> by the published identity key'}}, 'additionalProperties': False}
null_prekeys_fetch
NULL forward secrecy — fetch a peer prekey bundle (consumes one one-time key)
Fetches {spk, sigSpk, otk, otksLeft} for a recipient so you can start an X3DH-PQ forward-secret session (SDK: fs.startOutbound). ALWAYS fetch by META-ADDRESS: the sigSpk check verifies against the meta-address spendPub (sha256("null-fs-spk/v1:"+spk), secp256k1) and CANNOT run on a handle fetch (the SDK tags those fsUnverified — treat as unauthenticated keys). The nonce is MANDATORY and idempotent: a retry with the SAME nonce returns the SAME one-time key instead of draining the pool; use a fresh random 12-64 url-safe chars per new session. If otk comes back null the pool is empty or rate-limited (issuance is capped per recipient to slow drain attacks): proceed SPK-only — still forward-secret via the ratchet, slightly weaker for the first message — and the recipient replenishes automatically. A failed sigSpk check means a key-substituting relay: abort to the static seal and treat it as an incident, not a fallback. Read (consumes one otk per fresh nonce).
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['recipient', 'nonce'], 'properties': {'nonce': {'type': 'string', 'description': '12-64 url-safe chars; SAME nonce on retry = same key returned, no drain'}, 'recipient': {'type': 'string', 'description': 'st:eth:0xâ\x80¦ meta-address (REQUIRED for the SPK signature check; a handle fetch returns unverifiable keys)'}}, 'additionalProperties': False}
null_prekeys_publish
NULL forward secrecy — publish a PRE-SIGNED prekey bundle
Makes you reachable with forward secrecy: publishes your signed prekey bundle (medium-term spk + one-time otks) so peers can start X3DH-PQ sessions TO you. Generate and sign locally with the SDK (fs.genBundle + publishPrekeys — sigSpk is secp256k1 over sha256("null-fs-spk/v1:"+spk) by your spend key; sig is EIP-191 over the bundle statement). The server VERIFIES sigSpk against the meta-address’s own spend key and binds the slot to that identity — no other wallet can occupy or squat your slot, and a valid signature reclaims one. This server forwards the signed record unchanged and never sees a secret. Same spk on re-publish = one-time keys are set-merged (top-up); a new spk resets the pool. Monotonic by ts.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address', 'metaAddress', 'spk', 'sigSpk', 'otks', 'ts', 'sig'], 'properties': {'ts': {'type': 'number', 'description': 'unix seconds, ±10 min'}, 'sig': {'type': 'string', 'description': 'EIP-191 signature over the prekey statement by address'}, 'spk': {'type': 'string', 'description': 'base64 hybrid ML-KEM-768+X25519 pubkey'}, 'otks': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 50, 'minItems': 1, 'description': 'base64 one-time pubkeys'}, 'handle': {'type': 'string'}, 'sigSpk': {'type': 'string', 'description': 'compact secp256k1 hex over sha256("null-fs-spk/v1:"+spk) by the identity spend key'}, 'address': {'type': 'string'}, 'metaAddress': {'type': 'string', 'description': 'st:eth:0xâ\x80¦'}}, 'additionalProperties': False}
null_prov_issuer
NULL trust anchor - the ML-DSA-65 issuer key (pin it once)
Returns the post-quantum issuer public key that countersigns notary attestations, provenance mints and the witness-log head. Pin it once and verify everything against the pinned copy - a proof should never carry the key it wants to be checked against. Public on every lane.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_prov_mint
NULL Agent Wire - issuer-countersigned provenance for a claim YOU signed (lane)
Relays a provenance request you signed LOCALLY (SDK mintProvenance builds it): {meta, claim, ts, sig, bind, sig2}. A post-quantum identity MUST include sig2 (ML-DSA) or the issuer refuses. The issuer checks your signature + identity binding and countersigns - the claim is REGISTERED, not endorsed. ts must be current epoch-ms (+-10 min); claim values <=200 chars. Private-lane-only: use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['meta', 'claim', 'ts', 'sig', 'bind'], 'properties': {'ts': {'type': 'number', 'description': 'epoch ms, fresh'}, 'sig': {'type': 'string', 'description': 'secp256k1 compact signature over the mint hash, by your spend key (SDK)'}, 'bind': {'type': 'string', 'description': 'spend-key signature binding the issuer key (SDK)'}, 'meta': {'type': 'string', 'description': 'your st:eth:0x... meta-address'}, 'sig2': {'type': 'string', 'description': 'base64 ML-DSA-65 over null-prov-mint/v2|<meta>|<claimCanon>|<ts> - REQUIRED when your identity publishes a post-quantum key'}, 'claim': {'type': 'object', 'description': 'flat string claim, e.g. {model, purpose}', 'additionalProperties': {'type': 'string'}}}, 'additionalProperties': False}
null_transparency
NULL transparency - signed hashes of every served crypto artifact
The signed sha256 of every crypto artifact the server hands out (SDK, bundle, workers); hash changes are witness-chained under release:<file>. Fetch an artifact, hash it, compare - a mismatch means you were served something that is not the signed release.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_void_descriptor
NULL VOID - fetch a channel descriptor by handle (lane)
Returns a pseudonymous channel descriptor {descriptor, witness:{ts}}; the 3.3 KB ML-DSA signature and the handle-ownership proof come as separate parts (part=sig | part=proof) because they cannot share one 8 KiB lane reply. Verify all three locally (SDK voidVerifyDescriptor) before following. Private-lane-only (a direct lookup would tell the gateway which channel your IP wants): use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['handle'], 'properties': {'part': {'enum': ['sig', 'proof'], 'type': 'string', 'description': 'omit for the descriptor, or sig / proof'}, 'handle': {'type': 'string', 'description': 'the channel owner handle'}}, 'additionalProperties': False}
null_void_directory
NULL VOID - the opt-in channel directory (lane)
Channels whose creators SIGNED themselves discoverable (dark by default). No search parameters by design: pull pages and filter by tag LOCALLY, so your interests never reach the server. Opaque cursor, neutral order, no counts. Returns 404 if the directory is not switched on in this deployment, and PRIVATE_LANE_REQUIRED on BOTH doors until the route is on the relay allowlist (GET /api/ohttp/keys) - a pending server step. Private-lane-only: use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number'}, 'cursor': {'type': 'string', 'description': 'opaque cursor from the previous page'}}, 'additionalProperties': False}
null_void_publish
NULL VOID - publish a channel descriptor YOU signed (lane)
Relays {descriptor, proof:{ts, sig}} built and signed LOCALLY (SDK voidCreate + voidSignDescriptor + the handle-ownership proof). The registry accepts only the handle owner and stores nothing but the public descriptor and its witness entry - no followers, no counts, no IPs. Private-lane-only: use the stdio door.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['descriptor', 'proof'], 'properties': {'proof': {'type': 'object', 'required': ['ts', 'sig'], 'properties': {'ts': {'type': 'number'}, 'sig': {'type': 'string'}}, 'description': 'handle-ownership proof from the SDK', 'additionalProperties': False}, 'descriptor': {'type': 'object', 'description': 'the signed descriptor object from the SDK', 'additionalProperties': {}}}, 'additionalProperties': False}
null_witness_head
NULL transparency - signed head of the mailbox binding log
ML-DSA-signed head {seq, root, sig} of the append-only log that binds every mailbox record (slot|meta|kemPub|ts). Signed by the SAME issuer key as null_prov_issuer. Keep the last head you saw; a later head must extend it (null_witness_range) - a fork is proof of equivocation. Public on every lane so third-party auditors see the same log.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
null_witness_range
NULL transparency - hash-chained entries of the binding log
Up to 20 entries {s, b, r, t} from seq `from`: b binds slot|meta|kemPub|ts, r = sha256(prevRoot + b). Replay the chain from a head you trust to prove a mailbox binding was never silently swapped. Public on every lane.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'from': {'type': 'number', 'description': 'first seq (>=1, default 1)'}, 'limit': {'type': 'number', 'description': '1-20 (default 20)'}}, 'additionalProperties': False}
robyn_7702_check
Verify an EIP-7702 authorization
Check that a signed EIP-7702 authorization tuple recovers the expected account, and whether its nonce matches the live account nonce. Free, read-only, moves nothing.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['chainId', 'authorization'], 'properties': {'chainId': {'type': 'number', 'description': 'chain the authorization targets'}, 'authorization': {'type': 'object', 'required': ['address', 'nonce', 'yParity', 'r', 's'], 'properties': {'r': {'type': 'string'}, 's': {'type': 'string'}, 'nonce': {'type': ['number', 'string']}, 'address': {'type': 'string', 'description': 'the delegate contract'}, 'chainId': {'type': ['number', 'string']}, 'yParity': {'type': ['number', 'string']}}, 'description': 'the signed 7702 authorization tuple', 'additionalProperties': False}}, 'additionalProperties': False}
robyn_7702_delegate
EIP-7702 delegate + rail info
The canonical Robyn EIP-7702 batch-executor delegate: its address on each of the 22 EVM chains, the ABI, and the EIP-712 scheme for executeSigned. Delegate to this and the relayer can sponsor your transactions. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_attestation
Signed proof the router is live AND private, right now
Returns a relayer-SIGNED attestation that, as of a signed timestamp, every component was up (router, signing daemons, MCP, privacy relay) AND the privacy invariants held — the adversary probes could not distinguish cover traffic from real (classifier = chance) and the k-anonymity floor is enforced. Verify the signature yourself (recover the signer over the digest). Use this to programmatically decide whether to trust this router before routing value through it.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_capability_snapshot
What Robyn can actually do right now (signed)
A signed, timestamped record of current capability: which chains can actually be PAID OUT ON right now, which are merely policy-eligible, which rails are execute-ready, and whether delivery figures are measured or estimated. USE `serviceableNow`, NOT `policyEligible`, when deciding where to send funds — a chain can be eligible by policy while holding no inventory, in which case the instant lane is unavailable and the transfer falls through to a bridge rail. `notServiceable` lists the difference. Fetch this BEFORE committing to a multi-step plan and keep it with your decision: if the plan later fails you can show what you were told. It is a RECORD, not a guarantee — it does not promise the same capability a minute later, and the signature does not make it an SLA.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_changelog
What changed since I integrated?
Machine-readable API history. Pass the version your integration was built against as `since` and you get only what has changed after it, with an explicit `breaking` flag on each entry. CHECK `mustAct` FIRST: if true there are breaking changes and an existing integration may ALREADY be failing — read `entries[].action` for each. `breaking:true` means an existing correct integration could stop working; it is a compatibility claim, not a measure of importance.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'since': {'type': 'string', 'description': 'the API version you built against, e.g. "3.9.0"'}}, 'additionalProperties': False}
robyn_counterparty_check
Have I paid this address before?
Your OWN payment history with a recipient address: how many times, how recently, and whether this amount is typical. Call it before paying an address you have not confirmed. THIS IS NOT A REPUTATION SCORE and says nothing about whether the address is honest. A familiar address is NOT a safe address — keys get compromised. Never tell a user an address is "trusted" or "safe" on the basis of this. A `first-time-recipient` result is NOT a warning about the recipient — every legitimate relationship has a first payment. It is the moment to confirm the address through a second channel, because address substitution can only be caught before you send. Read `coverage`: float-lane payouts are NOT included, so "first time" can be wrong.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['toAddress'], 'properties': {'amount': {'type': 'string'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_cross_chain
Move value cross-chain, gasless
Plan a gasless cross-chain move and get the exact payload to sign. This hosted server never holds your key: call this, sign what it returns with your own wallet, then call robyn_submit to have the relayer broadcast it and pay the gas.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'fromToken', 'amount', 'toChain', 'toToken'], 'properties': {'amount': {'type': 'string', 'description': 'amount in fromToken base units'}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string', 'description': 'token address / symbol on the destination'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string', 'description': 'token address on the source chain'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_delivery_stats
Measured delivery times
How long settlements ACTUALLY take, per rail and per corridor — not a single advertised constant. CHECK `basis`/`status`: below the sample threshold this returns `insufficient-data` and the figure is a static ESTIMATE, not a measurement. Say which you are quoting when you tell a user how long something will take.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_errors
Error contract
The full error taxonomy: every errorCode, whether it is retryable, and the suggested recovery action. Read this once and branch on errorCode instead of parsing messages.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_evidence_bundle
One signed bundle of all evidence about a transfer
Assembles EVERYTHING about a settled transfer in one call: the on-chain verification, the unit-by-unit fee breakdown, what the alternative route would have cost, and whether the delivery time is measured or estimated — signed as a whole. This is the artefact to hand to a principal who was not there; swapping any component invalidates the signature. READ `verdict` BEFORE PRESENTING IT: the bundle verdict is the WEAKEST of its parts. A complete fee breakdown does not mean the transfer was confirmed — if `verdict` is `undetermined`, settlement was NOT verified and you must not describe it as complete. Components that could not be produced appear as `unavailable` with a reason; check `incomplete`.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'settled transfer id'}, 'minAmount': {'type': 'string', 'description': 'assert the minimum that should have arrived'}, 'recipient': {'type': 'string', 'description': 'assert who should have been paid'}}, 'additionalProperties': False}
robyn_fee_forensics
Where every unit of a fee went
Reconstruct a settled transfer unit by unit: destination payout gas, Robyn margin, or a Robyn SUBSIDY where Robyn absorbed a loss. Each line names who was paid and how the figure was derived. Anything that cannot be attributed is returned as `unattributed` rather than folded into another line — if you see that field, report it rather than presenting the breakdown as complete.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'settled transfer id'}}, 'additionalProperties': False}
robyn_improve_cost
What would make this transfer cheaper?
Turns a price into a decision. Returns concrete, QUANTIFIED changes — a cheaper destination chain with the exact saving, the size at which a fixed payout cost stops dominating, whether the instant float lane applies, and whether rails that would have competed were unavailable. CRITICAL: suggestions with `changesOutcome: true` move WHERE THE MONEY LANDS. Never apply those silently as cost savings — confirm with the user that the alternative destination is acceptable first, or you will have saved gas by delivering to the wrong place. If nothing can be improved it says so rather than inventing filler.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'toChain', 'amount'], 'properties': {'amount': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_integration_lint
Is the request I am about to send safe?
Post the request you INTEND to make and get back what is missing or unsafe, with the concrete consequence. Run this before your first live execute. Findings marked `unsafe` can lose money or make you report something untrue — fix them, do not proceed. IMPORTANT: it lints the REQUEST only. A clean lint does NOT mean your integration is correct — it cannot see whether you branch on all three verification verdicts or treat `undetermined` as success.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['endpoint', 'payload'], 'properties': {'payload': {'type': 'object', 'description': 'the body you intend to send', 'additionalProperties': {}}, 'endpoint': {'type': 'string', 'description': 'the endpoint you intend to call'}}, 'additionalProperties': False}
robyn_mandate_certificate
Signed proof the agent stayed within its budget
A signed certificate listing every spend counted against a mandate, the budget, the total spent, and whether it stayed inside. Hand it to the principal at the end of a period. Every spend listed was VERIFIED ON-CHAIN before counting, and the amount is what the chain showed arrived — not what the agent reported. IMPORTANT WHEN PRESENTING IT: this certifies adherence to a ROBYN budget. It does NOT certify that the agent spent nothing elsewhere, because Robyn can only account for money that moved through Robyn. Do not describe it as proof of total spending.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['mandateId'], 'properties': {'mandateId': {'type': 'string'}}, 'additionalProperties': False}
robyn_mandate_check
Does this spend fit the budget my principal set?
Check a proposed spend against a signed spending mandate BEFORE making it. Returns WITHIN_MANDATE, EXCEEDS_MANDATE or EXPIRED plus the remaining budget. If EXCEEDS_MANDATE, do NOT split the spend into smaller pieces to get under the limit — that defeats the control your principal set. Ask them to raise the budget. NOTE THE SCOPE: a mandate covers spending THROUGH ROBYN only. It is not custody and does not stop spending elsewhere with the same key.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['mandateId', 'amount'], 'properties': {'amount': {'type': 'string', 'description': 'proposed spend in base units'}, 'mandateId': {'type': 'string', 'description': 'the mandate digest'}}, 'additionalProperties': False}
robyn_mandate_cosign_request
Does this spend need the principal to approve it?
For mandates with a co-sign threshold, check whether a specific spend needs the principal to approve it and get the exact digest they must sign. The digest binds the mandate, the transfer AND the amount, so an approval cannot be reused for a different payment — do not attempt to reuse one. If a large spend is refused for want of a countersignature, present the digest to the principal rather than splitting the spend to slip under the threshold.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['mandateId', 'transferId', 'amount'], 'properties': {'amount': {'type': 'string'}, 'mandateId': {'type': 'string'}, 'transferId': {'type': 'string'}}, 'additionalProperties': False}
robyn_mandate_events
What has happened to my budgets
Poll for spend, nearly-exhausted, exhausted, approval-required and revoked events on a principal's mandates. Pass the returned `cursor` back as `since` for only what is new. Use this to tell a principal their budget is running low or that a large payment is waiting on their approval, instead of making them check each mandate by hand.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'number'}, 'since': {'type': 'string'}, 'principal': {'type': 'string'}}, 'additionalProperties': False}
robyn_mandate_list
Every budget a principal has granted
List all mandates granted by a principal address, with remaining budget, co-sign threshold, expiry and revocation state. Use this before telling a user they are safe: live mandates can still be drawn against WITHOUT further approval, and a forgotten grant is the one that hurts. Anything they no longer intend to honour should be revoked.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['principal'], 'properties': {'principal': {'type': 'string', 'description': 'the principal address'}}, 'additionalProperties': False}
robyn_mandate_status
How much of my budget is left?
Remaining and consumed budget for a signed mandate. Consumption counts ONLY transfers verified on-chain, so the figure cannot be inflated by claiming spends that did not happen.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['mandateId'], 'properties': {'mandateId': {'type': 'string'}}, 'additionalProperties': False}
robyn_mesh
Robyn mesh
List the Robyn gasless chains and the cross-chain route graph (22 EVM nodes + Stellar), plus the relayer/Permit2 addresses. No credentials needed.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_message_anchor_proof
Messaging v2 — anchoring proof for a feed row
Merkle inclusion proof for an anchored row id: leaf, path, root, the signer’s EIP-191 signature over the batch statement and the on-chain tx when enabled. Verify locally with plus-sdk verifyAnchorProof(). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': '16-hex feed row id'}}, 'additionalProperties': False}
robyn_message_directory
Messaging v2 — all mailboxes (oblivious lookup)
Every published v2 mailbox. PUBLIC rows carry {address, metaAddress, kemPub}; PRIVATE rows (the default since 2026-08-28) carry {handle, metaAddress, kemPub} and deliberately NO address. Identical for every reader, so fetching it reveals nothing about whom you intend to message — pick the recipient locally. Seal with the SDK: seal({metaAddress, kemPub}, {text, ts, from?, sig?}). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_message_erasure
Messaging v2 — signed proof of erasure
The last purge statement (expired count, cumulative, root of purged ids) signed by the operator. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_message_feed
Messaging v2 — public feed to scan with your viewing key
Returns released rows {id, ephemeralPubKey, viewTag, ct, releaseAt, nextAfter}, identical for every reader. Scan locally with the SDK (inbox(identity)) — checkStealthAddress with your viewPriv, then open ct with your KEM secret. Page with after=<nextAfter> (exact compound cursor — never skips same-tick rows); since=<releaseAt ms> also works but is best-effort at page boundaries. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'after': {'type': 'string', 'description': 'exact compound cursor from a prior pageâ\x80\x99s nextAfter (preferred for paging)'}, 'limit': {'type': 'number', 'description': '1â\x80\x93200, default 100'}, 'since': {'type': 'number', 'description': 'releaseAt cursor in ms (default 0)'}}, 'additionalProperties': False}
robyn_message_info
Sonar (private messenger) — status, suite and parameters
Sonar — PRIVATE · SEALED · POST-QUANTUM MESSENGER (broadcast to everyone, understood by one, remembered by none). Hybrid ML-KEM-768+X25519 encryption, a one-time stealth handle per message, fixed-size ciphertexts, 60 s release grid. The server stores only (ephemeralPubKey, viewTag, ct) — no sender, no recipient, no IP. Returns mode, ciphertext sizes, release grid, cover-row rate and the honest anonymity accounting (kContribution is 0: rotating handles give unlinkability, not extra participants). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_message_mailbox_of
Messaging v2 — resolve a Robyn name to its mailbox
For a Robyn name or NULL handle the server must resolve it, so this reveals your intended recipient to the server — prefer robyn_message_directory when you have an address. Returns {address|handle, metaAddress, kemPub} (private-handle rows carry no address by design). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['addressOrName'], 'properties': {'addressOrName': {'type': 'string', 'description': '0x address, a NULL handle (e.g. alice.null), or label.robyn.id / .robynchain.eth / .rhood.eth'}}, 'additionalProperties': False}
robyn_message_publish_mailbox
Messaging v2 — publish a PRE-SIGNED mailbox
Registers a mailbox so others can seal to you. PRIVATE BY DEFAULT: the server stores only a salted hash of your signing address — pass `handle` to be reachable by name (agents get the same handle claim browsers have), or `public:true` to bind your bare 0x address in the open directory instead. Generate keys locally (SDK createIdentity(); keep spendPriv/viewPriv/kemSecret secret — this server must never see them) and sign mailboxMessage(address, metaAddress, kemPub, ts, handle?) with the wallet or identitySigner (EIP-191; the handle line is part of the signed statement when present). Monotonic by ts: re-publish with fresh keys to rotate. Forwards the signed record unchanged.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address', 'metaAddress', 'kemPub', 'ts', 'sig'], 'properties': {'ts': {'type': 'number', 'description': 'unix seconds used in the signed message (±10 min)'}, 'sig': {'type': 'string', 'description': 'EIP-191 signature by address'}, 'handle': {'type': 'string', 'description': 'claim a reachable-by-name handle (3-32 chars a-z 0-9 . _ -); must be in the signed statement'}, 'kemPub': {'type': 'string', 'description': 'base64 hybrid ML-KEM-768+X25519 public key'}, 'public': {'type': 'boolean', 'description': 'true = legacy public mode: your 0x address appears in the directory'}, 'address': {'type': 'string'}, 'metaAddress': {'type': 'string', 'description': 'st:eth:0x<spendPub><viewPub>'}}, 'additionalProperties': False}
robyn_message_send
Messaging v2 — deliver an ALREADY-sealed message
Relays a message you sealed locally with /svc/msg2-sdk.mjs (seal(mailbox, inner) → {ephemeralPubKey, viewTag, ct}). This tool cannot encrypt for you: sending plaintext here would expose it to the relay, so it only accepts the sealed triple. Replay-idempotent (a resend returns duplicate:true). The message appears in the public feed at releaseAt. If you cannot run the SDK, use v1 (POST /api/messages/send) and know that v1 is plaintext.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['ephemeralPubKey', 'viewTag', 'ct'], 'properties': {'ct': {'type': 'string', 'description': 'base64 ciphertext from seal(); must be one of the fixed bucket sizes'}, 'viewTag': {'type': 'string', 'description': '0x + 1 byte from seal()'}, 'ephemeralPubKey': {'type': 'string', 'description': '0x + 33-byte compressed secp256k1 point from seal()'}}, 'additionalProperties': False}
robyn_netting_account
Netting balance, enrolment state and next nonce
Whether an address is enrolled (and therefore custodied), its internal balance, recent history, and `nextNonce` — which you MUST use when signing the next transfer or withdrawal. An address that never enrolled is reported as not custodied. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address'], 'properties': {'address': {'type': 'string', 'description': 'EVM address (0xâ\x80¦)'}}, 'additionalProperties': False}
robyn_netting_enroll_payload
Get the consent text a user must sign to open a netting account
Returns the EXACT message the account must sign with its OWN key to open a custodial balance. This endpoint holds no key and enrols nobody — it returns the text; the user signs it, then POST {address, signature} to /api/netting/enroll. CUSTODIAL — this is the ONE part of Robyn that holds your balance; every other tool here moves funds without Robyn ever holding them. Tell the user that plainly before they enrol. Show the user the full consent text before they sign it: it states that the balance is held by Robyn, is not insured, and could be lost.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address'], 'properties': {'address': {'type': 'string', 'description': 'the address that will own the netting account'}}, 'additionalProperties': False}
robyn_netting_info
What netting accounts are (opt-in, custodial)
Explains the opt-in netting ledger: transfers between two ENROLLED accounts settle as a book entry — no chain, no gas, no fee, instant, at ANY size including amounts below every per-chain cost floor. CUSTODIAL — this is the ONE part of Robyn that holds your balance; every other tool here moves funds without Robyn ever holding them. Tell the user that plainly before they enrol. Read-only. Returns the caps, the published limits and the fee model.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_netting_preview
What a netting withdrawal would actually deliver
Free and read-only. Given an amount, ranks EVERY exit chain by what actually arrives after the destination payout cost is deducted. Those costs differ by more than 1000x (Avalanche delivers ~$0.99994 of a dollar; Linea ~$0.927), so which chain you leave on is a real decision. Pass toChain to price one chain and learn whether it would succeed at all. Internal transfers between netting accounts remain free at any size — this cost applies only to leaving for a real on-chain balance.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['amount'], 'properties': {'amount': {'type': 'string', 'description': 'amount in USDC base units (6dp), e.g. "1000000" = $1.00'}, 'toChain': {'type': ['number', 'string'], 'description': 'price a single chain instead of ranking all'}}, 'additionalProperties': False}
robyn_netting_reserves
Proof of reserves for the custodial ledger
Publishes what Robyn OWES across all netting accounts against the real relayer float backing it, per chain. Solvency is checkable rather than asserted. Deposits are refused if they would push liabilities above a safe share of the float. Read-only — a user considering a custodial balance should be shown this.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_netting_statement
Full, untruncated netting history for an address
Internal transfers produce NO transaction hash because no transaction occurs — this append-only journal is their only record. Never truncated; page with `before` (a seq number). Use this when a user asks to verify or dispute an internal payment, since there is no chain to check.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address'], 'properties': {'limit': {'type': 'number', 'description': 'max entries (default 200)'}, 'before': {'type': 'string', 'description': 'return entries with seq below this, for paging'}, 'address': {'type': 'string', 'description': 'EVM address (0xâ\x80¦)'}}, 'additionalProperties': False}
robyn_netting_transfer_payload
Build the message to sign for a FREE internal transfer
Returns the exact string to sign, with the correct next nonce, for a free instant transfer between two ENROLLED accounts. Signs nothing and moves nothing — the sender signs the returned message, then POSTs {from,to,amount,nonce,signature} to /api/netting/transfer. BOTH parties must already be enrolled: Robyn will not hold a balance for a recipient who never consented, so to pay an unenrolled address use the ordinary non-custodial route instead.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['from', 'to', 'amount'], 'properties': {'to': {'type': 'string', 'description': 'recipient (must ALSO be enrolled)'}, 'from': {'type': 'string', 'description': 'sender (must be enrolled)'}, 'amount': {'type': 'string', 'description': 'USDC base units (6dp)'}}, 'additionalProperties': False}
robyn_payment_request_prepare
Prepare a payment request for the payee to sign
Build a canonical payment request (payee, chain, token, amount, memo, expiry) and return the digest for THE PAYEE to sign with their own wallet. Robyn does not sign these and holds no payee keys — a request signed by Robyn would prove nothing about the payee. Use this when an agent needs to ASK another agent for money in a way the payer can actually check.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['payee', 'chain', 'amount'], 'properties': {'memo': {'type': 'string'}, 'chain': {'type': ['number', 'string'], 'description': 'destination chain id or name'}, 'payee': {'type': 'string', 'description': 'address that should be paid'}, 'token': {'type': 'string'}, 'amount': {'type': 'string', 'description': 'base units'}, 'expiresInSec': {'type': 'number'}}, 'additionalProperties': False}
robyn_payment_request_settlement
Prove a payment request was satisfied on-chain
After paying, prove it: re-checks the transfer against the DESTINATION CHAIN and confirms the payee was paid at least the amount requested. Returns paid=true only on a verified on-chain result; paid=null means undetermined, which is NOT evidence you satisfied the request.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['request', 'signature', 'transferId'], 'properties': {'request': {'type': 'object', 'additionalProperties': {}}, 'signature': {'type': 'string'}, 'transferId': {'type': 'string', 'description': 'the transfer that paid it'}}, 'additionalProperties': False}
robyn_payment_request_verify
Verify a payment request before paying it
ALWAYS run this before paying a request you received. It confirms the payee address, chain, token and amount were signed by whoever controls the payee address, and that the request has not expired. If `signedByPayee` is false, DO NOT PAY — that is what an altered payee address looks like, and address substitution is the most common theft in this space. A valid signature proves AUTHENTICITY, not that the payment is owed and not that the payee is trustworthy.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['request', 'signature'], 'properties': {'request': {'type': 'object', 'description': 'the canonical request object', 'additionalProperties': {}}, 'signature': {'type': 'string', 'description': 'the payee signature'}}, 'additionalProperties': False}
robyn_plan
Validate a multi-step plan before executing any of it
Validate a WHOLE multi-step workflow up front instead of one hop at a time. Fees and durations accumulate across steps. Evaluation stops at the first unroutable step rather than reporting speculative results behind it. If the plan cannot work, the response names the BINDING CONSTRAINT and the value that would work (`bindingConstraint`, `whatWouldMakeThisWork`) — use that to adjust rather than retrying blindly. READ-ONLY: nothing is signed, reserved or moved. Use this before spending on step one.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['steps'], 'properties': {'steps': {'type': 'array', 'items': {'type': 'object', 'required': ['fromChain', 'toChain', 'amount'], 'properties': {'amount': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}, 'description': 'the hops, in order'}, 'constraints': {'type': 'object', 'properties': {'maxStepSeconds': {'type': 'number'}, 'maxTotalFeeBps': {'type': 'number'}, 'maxTotalSeconds': {'type': 'number'}, 'requireNonCustodial': {'type': 'boolean'}}, 'additionalProperties': False}}, 'additionalProperties': False}
robyn_plus_claim
Plus — claim blind signatures after paying
Submit BLINDED tokens (base64, from plus-sdk blindTokens()) with the payment txHash. Payment is verified on-chain (recipient, amount, confirmation; one tx pays one invoice), then each blinded token is signed blind. Unblind locally (plus-sdk claim() does all of this). This tool never sees an unblinded pass.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['invoiceId', 'blinded'], 'properties': {'txHash': {'type': 'string', 'description': 'EVM payment tx; omit for btc'}, 'blinded': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 500, 'minItems': 1}, 'invoiceId': {'type': 'string'}}, 'additionalProperties': False}
robyn_plus_info
Plus — what is sold, prices, mint key
Plus sells capacity (rate-limit-exempt sends), funded cover rows and signed/anchored Merkle proofs — never a "more private lane" (that would be a smaller crowd). Paid in ETH (Robinhood Chain, Ethereum, Arbitrum, Base), USDC (Base, Arbitrum) or BTC (Chainflip). Redeemed with RFC 9474 blind passes the server cannot link to any payment. Returns products, assets, the mint public key (JWK) and honest what-we-learn / what-we-do-not. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
robyn_plus_invoice
Plus — create an invoice
Creates an invoice for one bundle (500 passes, $3 quoted in the chosen asset). Returns {invoiceId, payTo, amount (base units), human, chainId, expires}. Pay from any wallet; then blind tokens locally with the SDK and call robyn_plus_claim. For btc pass refundAddress (your BTC address) — the invoice returns a Chainflip deposit address.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['asset'], 'properties': {'asset': {'enum': ['eth-4663', 'eth-1', 'eth-42161', 'eth-8453', 'usdc-8453', 'usdc-42161', 'btc'], 'type': 'string'}, 'refundAddress': {'type': 'string', 'description': 'btc only'}}, 'additionalProperties': False}
robyn_plus_invoice_status
Plus — invoice status
Status, remaining passes and payment details for an invoice. Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['invoiceId'], 'properties': {'invoiceId': {'type': 'string'}}, 'additionalProperties': False}
robyn_plus_trial
Plus — 20 FREE passes per day (no payment)
Try Plus before paying: submit up to 20 BLINDED tokens (base64, from plus-sdk blindTokens()) and receive blind signatures — identical unlinkable passes to paid ones. One trial per day per caller. Unblind locally (plus-sdk trial() does all of this). This tool never sees an unblinded pass.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['blinded'], 'properties': {'blinded': {'type': 'array', 'items': {'type': 'string'}, 'maxItems': 20, 'minItems': 1}}, 'additionalProperties': False}
robyn_preflight
Check a transfer will succeed BEFORE spending anything
Run this before robyn_prepare/robyn_submit. Returns decision GO or NO_GO plus typed `blockers` (each with a `fix`) and `warnings`. It catches, for free, the failures that otherwise cost gas: a fixed corridor fee that would consume the whole amount so nothing arrives, a recipient in the wrong address family, a corridor that can price but not settle, and a transfer above the instant lane's capacity that would silently pay a dearer bridge. Read-only — signs nothing, moves nothing. Pass fromAddress so membership (free micro-transfers) is recognised.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'toChain', 'amount'], 'properties': {'amount': {'type': 'string', 'description': 'amount in fromToken base units (e.g. "5000000" = 5 USDC)'}, 'toChain': {'type': ['number', 'string'], 'description': 'destination chain id or non-EVM name'}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string'], 'description': 'source chain id, or "solana"/"stellar"/"tron"/"bitcoin"'}, 'fromToken': {'type': 'string', 'description': 'symbol or address; omit for the chain default'}, 'toAddress': {'type': 'string', 'description': 'recipient â\x80\x94 validated against the destination chain family'}, 'fromAddress': {'type': 'string', 'description': 'sender â\x80\x94 determines membership and therefore fee tier'}}, 'additionalProperties': False}
robyn_preflight_full
Everything you should know before you move money
ONE call combining serviceability, routing competitiveness, cheaper alternatives, delivery basis and mandate budget into a single go/no-go. Call this before executing rather than making five separate checks. BLOCKERS AND WARNINGS ARE DIFFERENT. `blockers` WILL fail — do not attempt the transfer. `warnings` are things to tell the user or act on first; they do not prevent execution. Never present a warning as a failure or a blocker as advice. Anything in `unavailable` means a check could NOT run: treat it as unknown, not fine. `proceed:true` means nothing known blocks it — it is not a guarantee of success.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'toChain', 'amount'], 'properties': {'amount': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string'}, 'mandateId': {'type': 'string', 'description': 'check the spend against this budget too'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_prepare
Prepare a gasless action (returns what to sign)
Turn a plain-language or structured intent into a concrete plan plus the EXACT payload to sign. Costs nothing, moves nothing, needs no key. Returns status:"sign" with signRequest, or status:"quoted" if something is still missing.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'token': {'type': 'string', 'description': 'USDC, USDT, ETH, ...'}, 'amount': {'type': 'string', 'description': 'base units, overrides amountHuman'}, 'intent': {'type': 'string', 'description': 'plain language, e.g. "send 25 USDC to 0xabc... on arbitrum"'}, 'toChain': {'type': ['number', 'string']}, 'fromChain': {'type': ['number', 'string']}, 'toAddress': {'type': 'string'}, 'amountHuman': {'type': 'number', 'description': 'human units, e.g. 25 for 25 USDC'}}, 'additionalProperties': False}
robyn_privacy_posture
What is private, what is public — before you act
ONE read that tells you, for a chain and for the lane you reached Robyn on, exactly what stays private (relay lane, PQ transport, private mempool / sequencer) and what is still public (on-chain settlement, stealth is not PQ), the live mode of every privacy feature (messaging v2, Plus, netting-set shadow/live, cover rows), and how to raise your quota WITHOUT an identity (a blind Plus pass instead of an API key). Call it first when planning; it reads live flags, never a brochure.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'chainId': {'type': ['number', 'string'], 'description': 'chain to assess (e.g. 1, 8453, 42161)'}}, 'additionalProperties': False}
robyn_quote
Quote a gasless cross-chain route
Best gasless route to move a token from one Robyn chain to another. Returns estimated output, the bridge used, duration, and the Robyn fee. Read-only — moves nothing. IMPORTANT: check `quoteOnly` on the response. If it is true the corridor can be PRICED but NOT settled — execute will refuse it with UNSUPPORTED_DIRECTION — so present that quote as a price comparison only and do not tell the user it can be sent. `quoteOnlyReason` says why. Absent/false means executable.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'fromToken', 'toChain', 'toToken', 'amount'], 'properties': {'amount': {'type': 'string', 'description': 'amount in fromToken base units (e.g. "25000000" = 25 USDC)'}, 'toChain': {'type': ['number', 'string'], 'description': 'destination chain id, or "stellar"'}, 'toToken': {'type': 'string', 'description': 'token address / symbol on the destination'}, 'fromChain': {'type': ['number', 'string'], 'description': 'source chain id, or "stellar"'}, 'fromToken': {'type': 'string', 'description': 'token address on the source chain (0x0000â\x80¦0000 for native)'}, 'toAddress': {'type': 'string', 'description': 'recipient on the destination chain'}, 'fromAddress': {'type': 'string', 'description': 'sender â\x80\x94 determines membership (fee tier) AND whether a free netting path is available between these two accounts'}}, 'additionalProperties': False}
robyn_receipt_deliver
Deliver a settlement receipt to a counterparty, sealed
Hands a relayer-signed settlement receipt (from robyn_settle / a completed route) to the counterparty's sealed messaging-v2 mailbox, so they get verifiable proof (terms honored, authorized, clean provenance) WITHOUT ever contacting Robyn. Same wire shape as any message; content-hash idempotent. Only receipts signed by this relayer are accepted.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['to'], 'properties': {'to': {'type': 'string', 'description': 'counterparty address or Robyn name with a v2 mailbox'}, 'pass': {'description': 'optional Plus pass {preparedMsg,sig} to skip the lane rate limit'}, 'receipt': {'description': 'the signed receipt object'}}, 'additionalProperties': False}
robyn_receipt_verify
Verify a settlement receipt
Checks digest + relayer signature + signed terms of a receipt you received (e.g. opened from your v2 mailbox). Read-only.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'receipt': {}}, 'additionalProperties': False}
robyn_recipes
The right order to call things
Ordered playbooks for real goals: pay-someone-safely, prove-what-i-spent, spend-within-a-budget, handle-failures-well, stay-current. CALL THIS BEFORE IMPROVISING A SEQUENCE. Each step says what it answers, what to do with the answer, whether it is optional, and what skipping it costs. Steps marked optional:false should not be skipped — `skippingCosts` explains the concrete harm, not a style preference.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'name': {'type': 'string', 'description': 'a specific recipe, or omit for all'}}, 'additionalProperties': False}
robyn_refusal_verify
Verify a refusal receipt
Check a signed refusal receipt. Send header `x-anygas-receipt: 1` on any request and, IF Robyn refuses it, the error response carries a signed `refusalReceipt` recording what was asked, when, and why. This matters because when a provider says no, the AGENT gets the blame — a receipt lets you prove to your principal that you were blocked externally rather than simply failing. It proves the refusal HAPPENED; it does not claim the refusal was correct.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['receipt'], 'properties': {'receipt': {'type': 'object', 'description': 'the full refusalReceipt object as returned', 'additionalProperties': {}}}, 'additionalProperties': False}
robyn_route_status
Track a cross-chain route
Status of an in-flight route by id (BRIDGING → DONE), with the destination tx once delivered.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string'}}, 'additionalProperties': False}
robyn_sandbox_do
Dry-run the whole flow with no funds
Runs the identical path end to end against the sandbox: no key, no funds, no broadcast. Use this to prove an integration works before touching real money.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'token': {'type': 'string'}, 'amount': {'type': 'string'}, 'intent': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'fromChain': {'type': ['number', 'string']}, 'toAddress': {'type': 'string'}, 'amountHuman': {'type': 'number'}}, 'additionalProperties': False}
robyn_settle
Settle value privately, gasless, best-route — one call
The one-verb primitive. Say where value should go; Robyn returns the best route (all rails compared), the gasless method (no native token needed), the privacy posture that will apply (API-relay + private mempool where available + uniform shape), and what the settlement receipt will prove — in a SINGLE call. It collapses quote + preflight + prepare. Planning only: it never broadcasts — sign + submit via robyn_submit. Add private:true to request private-mempool execution where an endpoint exists.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['amount', 'fromChain', 'toChain', 'toAddress'], 'properties': {'amount': {'type': 'string', 'description': 'value in source-token base units (e.g. "25000000" = 25 USDC)'}, 'private': {'type': 'boolean', 'description': 'request private-mempool execution (default: auto where an endpoint exists)'}, 'toChain': {'type': ['number', 'string'], 'description': 'destination chain id or non-EVM name'}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string'], 'description': 'source chain id or "stellar"/"solana"/"tron"/"bitcoin"'}, 'fromToken': {'type': 'string', 'description': 'symbol or address; omit for the chain default (USDC)'}, 'toAddress': {'type': 'string', 'description': 'recipient on the destination'}, 'fromAddress': {'type': 'string', 'description': 'sender â\x80\x94 sets fee tier and free-netting eligibility'}}, 'additionalProperties': False}
robyn_spend_statement
Signed proof of what was spent
A statement of every transfer in a window with each fee broken down, SIGNED by Robyn's relayer key (EIP-191). Use this when you must PROVE to a principal what you spent — your own summary is a claim by the party being audited, but this is verifiable against a published address without trusting you or Robyn. Read `limitations` and repeat them: the statement covers the Robyn float lane only and excludes other rails and the custodial netting book, so it may not be a complete picture of activity.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'days': {'type': 'number', 'description': 'window length, default 30, max 365'}, 'address': {'type': 'string', 'description': 'restrict to transfers whose record names this sender'}}, 'additionalProperties': False}
robyn_sponsor_7702
Sponsor a transaction (relayer pays the gas)
Price or request an EIP-7702 sponsored transaction: Robyn submits your signed authorization as a type-4 transaction and PAYS THE GAS, so your account needs no native token. Over this HOSTED endpoint the call is a DRY price-check (returns estGas, priceUsd and the exact envelope) — paying the x402 invoice to broadcast requires calling POST /api/7702/sponsor directly with an X-PAYMENT header.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['chainId', 'authorization'], 'properties': {'to': {'type': 'string', 'description': 'call target (defaults to the delegated account itself)'}, 'data': {'type': 'string', 'description': 'calldata hex'}, 'chainId': {'type': 'number'}, 'authorization': {'type': 'object', 'required': ['address', 'nonce', 'yParity', 'r', 's'], 'properties': {'r': {'type': 'string'}, 's': {'type': 'string'}, 'nonce': {'type': ['number', 'string']}, 'address': {'type': 'string'}, 'chainId': {'type': ['number', 'string']}, 'yParity': {'type': ['number', 'string']}}, 'additionalProperties': False}}, 'additionalProperties': False}
robyn_submit
Submit your signed intent (relayer pays the gas)
Relay an intent you already signed. The relayer broadcasts it and fronts all network gas; your account needs no native token. Build `permit2` from robyn_prepare: sign its signRequest.eip712 payload (canonical Permit2 domain + PermitTransferFrom/TokenPermissions types) and pass the OBJECT below - not a bare signature string. The signed spender must be the relayer from signRequest.spender, otherwise the permit cannot be redeemed. Supply idempotencyKey so a retry after a timeout cannot double-spend. TO REHEARSE WITHOUT BROADCASTING set dryRun:true — it returns {status:"DRY", broadcast:false, wouldSend} and moves nothing, on EVERY corridor. Do NOT assume that omitting a live flag means dry: that holds on the float lane and the non-EVM legs, but the EVM-to-EVM path ignores it and BROADCASTS.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'toChain', 'fromToken', 'toToken', 'amount', 'toAddress', 'permit2'], 'properties': {'amount': {'type': 'string'}, 'dryRun': {'type': 'boolean', 'description': 'true = rehearse only: returns {status:"DRY", broadcast:false, wouldSend} and broadcasts NOTHING, on every corridor. Use this to preview before committing.'}, 'permit2': {'type': 'object', 'required': ['owner', 'permitted', 'nonce', 'deadline', 'signature'], 'properties': {'nonce': {'type': 'string', 'description': 'the nonce from signRequest.eip712.value.nonce'}, 'owner': {'type': 'string', 'description': 'address that signed the permit'}, 'deadline': {'type': 'string', 'description': 'the deadline from signRequest.eip712.value.deadline'}, 'permitted': {'type': 'object', 'required': ['token', 'amount'], 'properties': {'token': {'type': 'string', 'description': 'ERC-20 being permitted (signRequest.tokenAddress)'}, 'amount': {'type': 'string', 'description': 'exact base-unit amount (signRequest.amount)'}}, 'additionalProperties': False}, 'signature': {'type': 'string', 'description': '0xâ\x80¦ signature over signRequest.eip712'}}, 'description': 'Permit2 SignatureTransfer object - NOT a bare signature string', 'additionalProperties': False}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string'}, 'toAddress': {'type': 'string'}, 'idempotencyKey': {'type': 'string', 'description': 'any unique string; makes retries safe'}}, 'additionalProperties': False}
robyn_verify_outcome
Verify a transfer against the chain
Check what ACTUALLY happened to a settled transfer, against the destination chain rather than Robyn's own database. Optionally assert who should have been paid (`recipient`) and the minimum that should have arrived (`minAmount`); we decode the payout transaction's ERC-20 Transfer logs and report whether reality matches. Also cross-checks Robyn's own receipt against the chain and says so if the books disagree. THE VERDICT IS THREE-VALUED: `verified`, `failed`, or `undetermined`. Treat `undetermined` as UNKNOWN, never as success — it means the chain was unreachable, the tx is not mined, or the rail records completion as a balance delta that cannot be re-derived (Allbridge/Chainflip/Solana/Tron). Do not tell a user a transfer is confirmed on an undetermined result.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'transfer id, or the source/destination tx hash'}, 'minAmount': {'type': 'string', 'description': 'minimum base units that must have arrived'}, 'recipient': {'type': 'string', 'description': 'address that must have been credited'}}, 'additionalProperties': False}
robyn_vip_status
Check membership / VIP benefits for an address
Check whether an address holds a recognised member NFT and what it gets. Members pay ZERO on cross-chain transfers of $0.10-$25 to low-cost chains, 15bps instead of 25bps routing, and 10% instead of 25% gas markup. Read-only. Call this before quoting for a user so you can tell them accurately what a transfer will cost — and, if they are not a member, what holding a recognised NFT would save them.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['address'], 'properties': {'address': {'type': 'string', 'description': 'EVM address (0xâ\x80¦) to check'}}, 'additionalProperties': False}
robyn_why_this_route
Why this route won — and what it beat
Returns the full routing decision: every rail that quoted, what each would deliver, the margin the winner won by, and which rails stayed SILENT and why. Signed, so you can archive the rationale. CHECK `wasCompetitive` BEFORE TELLING A USER THE PRICE IS GOOD. If it is false, exactly one rail answered and "best" means "only" — it did not beat anything. Rails in `silentRails` did NOT lose; they failed to answer (down, rate-limited, missing credentials). Never describe them as more expensive.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fromChain', 'toChain', 'amount'], 'properties': {'amount': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'toToken': {'type': 'string'}, 'fromChain': {'type': ['number', 'string']}, 'fromToken': {'type': 'string'}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_yield_account
Non-custodial yield account
An agent's own Aave v3 / Moonwell position (aUSDC/mUSDC) per chain + the capped allowance it granted the relayer + live APY (best-yield auto-selected). Non-custodial: funds stay in the agent's wallet, Robyn holds no key and no pool.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['agent'], 'properties': {'agent': {'type': 'string', 'description': 'the agent wallet address (0xâ\x80¦)'}}, 'additionalProperties': False}
robyn_yield_quote
Quote a spend from yield
Read-only JIT quote: how a spend would be fulfilled from an agent's Aave yield venue (draw <= your allowance -> Aave/Moonwell withdraw -> gasless deliver). Moves nothing.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['agent', 'srcChain', 'amount'], 'properties': {'agent': {'type': 'string'}, 'amount': {'type': 'string', 'description': 'USDC base units (6dp)'}, 'toChain': {'type': ['number', 'string']}, 'srcChain': {'type': ['number', 'string']}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
robyn_yield_spend
Spend from yield (one signature)
Spend from your yield (Aave v3 or Moonwell) with ONE EIP-712 signature: Robyn pulls only up to your on-chain aUSDC/mUSDC allowance, unwinds exactly what is needed, and delivers gaslessly; the remainder keeps earning. This HOSTED endpoint is READ-ONLY: it returns the exact EIP-712 intent to sign + a live quote. To execute, sign it and POST {intent,signature,live:true} to /svc/api/ncaccount/spend, or run `npx anygas-mcp` locally with ROBYN_SIGNER_KEY. One-time setup: supply USDC to Aave v3 or Moonwell in your wallet + approve the relayer for your aUSDC/mUSDC up to your risk budget.
Eingabeschema 
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['agent', 'srcChain', 'amount'], 'properties': {'agent': {'type': 'string'}, 'amount': {'type': 'string'}, 'toChain': {'type': ['number', 'string']}, 'srcChain': {'type': ['number', 'string']}, 'toAddress': {'type': 'string'}}, 'additionalProperties': False}
Verlauf

Letzte Tool-Änderungen

Hinzugefügt
null_market_delist
29. September 2026 02:56
Hinzugefügt
null_market_list
29. September 2026 02:56
Hinzugefügt
null_market_listings
29. September 2026 02:56
Hinzugefügt
null_void_publish
29. September 2026 02:56
Hinzugefügt
null_void_directory
29. September 2026 02:56
Hinzugefügt
null_void_descriptor
29. September 2026 02:56
Hinzugefügt
null_calls_info
29. September 2026 02:56
Hinzugefügt
null_capsule_cancel
29. September 2026 02:56
Hinzugefügt
null_transparency
29. September 2026 02:56
Hinzugefügt
null_witness_range
29. September 2026 02:56
Hinzugefügt
null_witness_head
29. September 2026 02:56
Hinzugefügt
null_login_verify
29. September 2026 02:56
Hinzugefügt
null_prov_mint
29. September 2026 02:56
Hinzugefügt
null_prov_issuer
29. September 2026 02:56
Hinzugefügt
null_notarize
29. September 2026 02:56
Hinzugefügt
null_agent_guide
17. September 2026 12:45
Hinzugefügt
null_balance
17. September 2026 12:45
Hinzugefügt
null_prekeys_publish
17. September 2026 12:45
Hinzugefügt
null_prekeys_fetch
17. September 2026 12:45
Hinzugefügt
null_names_market
17. September 2026 12:45
Hinzugefügt
null_names_quote
17. September 2026 12:45
Hinzugefügt
null_ecosystem
17. September 2026 12:45
Hinzugefügt
robyn_message_erasure
17. September 2026 12:45
Hinzugefügt
robyn_message_anchor_proof
17. September 2026 12:45
Hinzugefügt
robyn_plus_claim
17. September 2026 12:45
Hinzugefügt
robyn_plus_trial
17. September 2026 12:45
Hinzugefügt
robyn_plus_invoice_status
17. September 2026 12:45
Hinzugefügt
robyn_plus_invoice
17. September 2026 12:45
Hinzugefügt
robyn_plus_info
17. September 2026 12:45
Hinzugefügt
robyn_message_publish_mailbox
17. September 2026 12:45
Entdecken

Ähnliche MCP-Server

x402-endpoints

io.github.digitalweb33333-creator/x402-endpoints

Offers paid x402 API tools for crypto intelligence, wallet and transaction analysis, compliance screening, content safety, due di…

Cofferline

com.cofferline/treasury

Provides policy-controlled agent wallet treasury operations, token conversions, gas top-ups, prediction-market orders, delegation…

biii

io.github.philpof102-svg/biii

Evaluates Base wallets, tokens, agents, merchants, payment authorization, transaction settlement, approvals, theft traces, and on…

Agent Control — Agent Meter

net.agent-control/agent-control

Provides agent payment-risk checks, transfer approval workflows, USDC billing, payment-address scanning, signed receipts, and sub…

SafeRoute

io.github.crystalsignal/saferoute

Provides safety checks, simulation, routing, and intent verification for noncustodial USDC payments and swaps on Base.

x402-solana

io.github.digitalweb33333-creator/x402-solana

Provides paid tools for crypto token safety, Solana and EVM pre-trade checks, market data, sanctions screening, KYB lookups, and …

aml

com.oceanalt/aml

Screens blockchain addresses and payment endpoints, decodes transaction intent, verifies x402 payment requirements, and produces …

paycrow

io.github.michu5696/paycrow

Creates and manages USDC escrow payments on Base with delivery confirmation, disputes, trust scoring, protected calls, and servic…