Fides

Build complete agent transaction flows across MCP, payment rails and onchain actions, with authorization built into the execution path.

[Fides @fidesbuilder]

FIDES is live on Robinhood Chain via Pons.

Build complete agent transaction flows across MCP, x402 and onchain actions, with authorization built into the execution path.

- owner sets budget, assets, contracts, services, limits and expiry, and signs once
- agent actions are built into one execution plan
- every action is checked against the signed FIDES before it runs
- compatible calls and payments are grouped
- only the required transactions go onchain

agent workflow → FIDES Builder → group + verify → execute

contracts deployed and source-verified on mainnet. app, SDK, CLI, API and Claude extension available now.

https://t.co/hOfT921NMS

OFFICIAL CA : 0x44114d6f66202a267b92bdbb57ae81480a86f0b3

[Fides @fidesbuilder]

What you can do with FIDES. Live on Robinhood Chain.

01 / Agent Authorization
Set budgets, approved contracts, assets and expiry. Agents execute within signed limits. Anything outside gets rejected.

02 / Payment rails
Agents pay for APIs and services directly from their authorized budget. Every payment tracked.

03 / MCP Execution
Every tool call checked against FIDES policy before reaching the MCP server.

04 / Transaction Builder
Plans, verifies, simulates and groups agent actions into fewer onchain transactions.

05 / Gasless Execution
Hosted relayer handles submission. Agent keys need zero ETH.

06 / Claude Integration
Run authorized workflows directly from Claude Desktop or Claude Code.

07 / Receipts & Revocation
Track spending, inspect executions, withdraw funds or revoke permissions anytime.

Built in-house:
Transaction Builder, FIDES Account, Verifier, policy contracts, SDK, CLI, API, MCP + x402 adapters.

One signed authorization across the entire execution path.

FIDES - Transaction Builder for autonomous agents.

https://t.co/LNVWawaqqV

[Fides @fidesbuilder]

First FIDES transactions on Robinhood Chain. Executed entirely through Claude set up as an example.

One prompt. Plain English.

1. Authorization
Signed one FIDES:
• 2.7 USDG budget
• Paid API capped at 0.1 USDG
• 7-day expiry

2. Paid API
Claude purchased live chain data through a paid API. 0.01 USDG deducted from the budget.

3. Transaction Builder
Claude planned 4 payments.

• 3 passed FIDES authorization checks
• 1 exceeded the budget (3 USDG) - blocked before execution

4. Execution
• Transactions simulated before submission
• 3 payments grouped into 1 onchain transaction
• Gas covered by the FIDES relayer
• No ETH required by the agent

Remaining budget: 2.08 / 2.7 USDG

MCP tools, paid APIs and onchain payments operating under one signed authorization.

First execution, verifiable onchain.

TX: https://t.co/EPgmfDA3rs

Docs: https://t.co/LNVWawaqqV

[Fides @fidesbuilder]

FIDES is on npm. 📦

Our own Transaction Builder for autonomous agents. Live on Robinhood Chain.

Agents doing real work fire off a pile of separate actions.
Every one is its own signature, its own transaction, its own gas.

FIDES builds them into one.

Example: an agent runs weekly payouts.
5 contributors, 2 invoices. 7 payments in USDG.

Without FIDES:
→ 7 approvals from you
→ 7 separate transactions
→ 7 gas payments, so the agent needs ETH
→ an agent wallet that can send anything, anywhere

With FIDES:
→ you sign once: 500 USDG a week, these addresses only, 30 days
→ the agent plans all 7 payments
→ Builder checks each one against your limits and simulates the batch
→ 7 payments go out as 1 transaction
→ gas paid by the relayer, agent holds 0 ETH

The agent then tries an 8th payment to an address you never allowed.
Blocked. Never sent.

Same path for MCP tool calls, agent payment rails and contract calls.

The FIDES Stack, all built in-house:

◈ @fidesbuild/core: FIDES format, EIP-712, Builder planning
◈ @fidesbuild/contracts: deployed contracts on Robinhood Chain
◈ @fidesbuild/sdk: create, verify, build, simulate, execute
◈ @fidesbuild/x402: agent payments inside signed budgets
◈ @fidesbuild/mcp: every MCP tool call checked first
◈ @fidesbuild/cli: run and manage it from the terminal
◈ @fidesbuild/mcp-server: Claude integration, gasless execution

Not a wallet. Not an agent.
The execution layer agents run through.

📦 npm i @fidesbuild/sdk

https://t.co/Ro86jUmfLU
https://t.co/xAP4GRkK7w

[Fides @fidesbuilder]

we didn't launch FIDES with one way in. we launched with three.

app: create and sign a FIDES, fund your FIDES Account, run transfers and contract calls, withdraw or revoke. connect a wallet, nothing to install.

claude: add the FIDES extension to Claude Desktop, or in Claude Code:

claude mcp add fides -- npx -y @fidesbuild/mcp-server@latest

then say "Set up FIDES" and sign your limits once.

sdk / cli / api: for agent builders. MCP and payment adapters included, plus a hosted relayer so your agent needs no gas.

npm install @fidesbuild/sdk viem

same signed FIDES across all three. funds stay in your account.

install and setup:

https://t.co/3cmzA8kHeb

[Fides @fidesbuilder]

dexscreener updated and paid.

[Fides @fidesbuilder]

Team tokens officially burned. Verifiable onchain.

$FIDES is live on Robinhood Chain.

Transaction infrastructure for autonomous agents. One Builder for MCP, x402 and onchain execution, with authorization built into every step.

https://t.co/hOfT921NMS

Burn TX:
https://t.co/PMFPqxRoZQ

[Fides @fidesbuilder]

fides is a transaction builder for autonomous agents.

the user sets budget, assets, contracts, services, limits and expiry. agent actions are built into one execution plan. every action is checked against the original oath, compatible calls and payments are grouped, and only the required transactions go onchain.

agent workflow → oath builder → group + verify → execute

[Fides @fidesbuilder]

fides contracts are on robinhood chain mainnet

factory 0x5acc1cf7bb580ffeedd2d1a0d325f57254ac54ca

account impl 0x861fb06b7a28c770d0fcc05ee75ecab06fe50f86

verifier 0xb31b4add508b12bb92eb8c3dcc370e9fe9723274

policy 0x29a127fdbc885ba78b11b04447d5ca0be346f5a6

revocation 0xe7432ae5d7b16f888e9cea070cf4cb2d60ea2cf6

receipts 0xe94cd83415a585f2a2b06315411056a42f9327e0

accounts are 1167 clones off the factory, one per owner, address is deterministic.

owner signs one eip-712 scope: agent key, spend caps, target + selector allowlist, services, max actions, expiry.
agent signs bundles against it. the account checks every call against the scope, counts spend by balance delta,
bitmap nonces for replay. anyone can relay, relayer has no authority.

sigs go ecdsa first, then 1271. revoke is one tx from the owner.

solc 0.8.28, via-ir, 800 runs. verified on sourcify, exact match on creation + runtime:

https://t.co/xVz8JxS8f3

[Fides @fidesbuilder]

FIDES

Transaction Builder for autonomous agents.

Builds complete agent transaction flows across MCP, x402 and onchain actions, with authorization built into the execution path.

• User sets budget, assets, contracts, services, limits and expiry
• Agent actions are built into one execution plan
• Compatible calls and payments are grouped through the Transaction Builder
• One authorization can cover the full workflow
• Removes repeated approvals, signatures and unnecessary transaction steps
• Every action is checked against the original FIDES before execution
• Only the required transactions are sent onchain

Agent workflow → FIDES Builder → Group + Verify → Execute

[Fides @fidesbuilder]

24/7 agent loops make execution permissions even more important.

robinhood is bringing trade approvals into agents. oath extends that idea to onchain workflows.

one owner-signed boundary for budgets, contracts, services and expiry. every mcp, x402 and onchain action verified before execution.

[Robinhood @RobinhoodApp]

Introducing Robinhood Agents. 🔥

With Agents, anyone can now build their own agent directly inside Robinhood and get started with agentic trading. You can:

- Create an agent in just a few taps, no technical setup required
- Analyze, strategize, and execute through your agent
- Create Loops that let your agent run 24/7
- Have safety built in with a dedicated account and trade approvals

Coming soon.

[Fides @fidesbuilder]

an agent doing one job doesn't make one transaction.

it calls a service, pays for it, approves a token, calls a contract, pays again. every step is its own approval, its own signature, its own transaction.

nothing looks at the whole workflow before it starts hitting the chain.