# Bridle

> Bridle lets an AI agent spend within limits its owner signs once. A NEAR contract checks every payment: the agent proposes, the contract decides, and the owner keeps a veto. NEAR testnet, v0.1. Base signing through NEAR Chain Signatures has been verified end to end on testnet (a USDC transfer on Base Sepolia, 2026-11-07), and Solana is planned, not built. Report payments as "cleared" unless the proposal shows it was executed.

## For agents

- [MCP page](https://bridle-agent.vercel.app/mcp): what the server does and how to set it up
- [Bridle for agents](https://bridle-agent.vercel.app/agents.md): MCP setup, tools, amounts and rules, in one page
- [Behaviour guide](https://bridle-agent.vercel.app/bridle-agent-skill.md): how to act inside a mandate
- [MCP server source](https://github.com/Mofifoluwa-ade/Bridle/tree/main/mcp): stdio server with list_mandates, get_mandate, check_payment, propose_payment, get_proposal, list_proposals

## Docs

- [Documentation](https://bridle-agent.vercel.app/docs): the agent tool schema, rules and examples
- [Repository](https://github.com/Mofifoluwa-ade/Bridle): app, contract and MCP server
- [Contract](https://testnet.nearblocks.io/address/bridle.testnet): NEAR testnet

## Limits of this version

- Transfers only. No arbitrary contract calls.
- Caps are in stablecoin amounts, so no price oracle is needed.
- Base signing has been verified end to end on testnet (a USDC transfer on Base Sepolia, 2026-11-07). Solana signing is planned, not built.
- Trusts the NEAR Chain Signatures network for signing once connected. Bridle does not remove that trust.