Loops HouseMeridian

NEAR HACKATHON
Links
Team
1 member- VIOwner
Vivek B R
Overview
Meridian gives AI agents a wallet with rules they cannot break.
Problem: agents can now pay for APIs, compute and other agents, but giving an agent a key is all-or-nothing. One prompt injection can drain it, and spending rules written in a prompt are only suggestions.
What we built: a Vault smart contract on NEAR testnet (vault.vivek-meridian.testnet) that holds funds and enforces a mandate per agent: budget, per-transaction cap, daily cap, vendor allowlist and approval threshold. The agent's NEAR account only holds a function-call access key restricted to the Vault, so it cannot move money any other way. Blocked payments are logged on-chain with the exact rule that stopped them (NEP-297 events).
On top of the Vault:
- Agents pay APIs with HTTP 402-style payments, verified on-chain by the vendor.
- Agents hire other agents: tasks, bids, a counter-offer, on-chain escrow and release.
- Sub-mandates delegate budget, but only with equal or narrower limits.
- Payments above the threshold wait for owner approval.
- Owners can write rules in plain English; NEAR AI Cloud turns them into exact mandate fields for review.
- The agents themselves run on NEAR AI Cloud.
Break Meridian (live): https://meridian-zeta-murex.vercel.app/break lets anyone try to talk the agent into paying them. The agent can be fooled, and sometimes is. The Vault still decides on-chain, and money can never reach an address the attacker chooses.
Chain Signatures: Vault-side authorization of foreign payments and Sepolia address derivation are implemented; MPC signing is in progress and documented in the README.
Stack: Rust (near-sdk, cargo-near), TypeScript agents, Next.js dashboard on Vercel, Upstash Redis. 54 contract tests. Built with Claude Code.