RYCORE simulates every transaction your agent wants to make, checks it against your policy, and only signs when it passes. Denied means no signature — ever.
Your agent never holds a private key. It asks RYCORE to sign — and RYCORE decides.
The agent sends the transaction it wants to make — to, value, data — to RYCORE instead of signing it itself.
The transaction is simulated against live chain state and checked against your versioned policy: value limits, daily spend, blocked patterns.
ALLOW signs with the enforced signer. DENY returns no signature. REQUIRE_APPROVAL waits for your one-time approval.
Not a dashboard that watches. A gate that acts.
Signer wallets live inside RYCORE, keys encrypted with AES-256-GCM. The agent never touches a private key.
Policies are versioned and immutable. Change the rules by publishing a new version — never by editing history.
Large transactions need your Ed25519 approval, bound to that exact transaction hash. A token works once, then it is spent.
If pricing, simulation, or the RPC fails, the answer is DENY. RYCORE never signs when it cannot verify.
Reads fall through multiple Robinhood Chain RPC endpoints, so one rate limit does not stop the check.
RYCORE is infrastructure, not a token sale. Your agent, your policy, your keys.
Two calls. The second one only signs if the policy allows it.
# 1. Create a signer wallet (keys shown once — save them) curl -X POST https://rycore-api.rycore.workers.dev/v1/signers \ -H "X-API-Key: ryc_live_..." # 2. Ask RYCORE to sign — it evaluates first curl -X POST https://rycore-api.rycore.workers.dev/v1/transactions/sign \ -H "X-API-Key: ryc_live_..." \ -d '{"from": "0x...", "to": "0x...", "value": "10000000000000000"}'
The API is free while in beta. A paid tier comes later — the free tier stays.