尚未检测到更新。GitHub 发布版本后会显示在这里。
正在加载完整 README。 以下为已保存的摘录。
The control plane for AI agent payments. Rein sets the rules, watches every payment, and scores every counterparty — so agents can transact at machine speed without machine-speed losses.
Rein is developer tooling and middleware for the agentic payments economy (the x402 / ERC-8004 stack). It is non-custodial: Rein governs an agent's authority to spend, never the funds themselves.查看完整 README ↗The control plane for AI agent payments. Rein sets the rules, watches every payment, and scores every counterparty — so agents can transact at machine speed without machine-speed losses.
Rein is developer tooling and middleware for the agentic payments economy (the x402 / ERC-8004 stack). It is non-custodial: Rein governs an agent's authority to spend, never the funds themselves. The whole design in one document: the whitepaper (PDF).
Status: v0.3 — all three phases have shipped their first cut, and a hosted engine runs an invited beta. Advisory SDK-mode + full observability, end to end — fully offline on mock rails, and live on real x402 rails on Base Sepolia (EIP-3009 USDC settled by the hosted x402.org facilitator — on both sides: the guarded agent and a
@reinconsole/gate-monetized vendor). The session-key signer tier — the GA enforcement architecture, where the wallet key leaves the agent entirely — ships as@reinconsole/signer. The supply side ships as@reinconsole/gate, vendor monetization middleware (Phase 2). The stack is durable:@reinconsole/storepersists the engine (agents, policies, spend, the signed decision chain), the reputation evidence, gate receipts + replay slots, and signer sessions across restarts. And@reinconsole/graph(Phase 3) turns the receipts both sides produce into explainable reputation scores that feed back into enforcement:vendorReputationLtpolicies on the agent side, payer screening at the vendor's door. Identity is on-chain:@reinconsole/erc8004keys reputation by ratified ERC-8004 registrations — verified live against the real Base Sepolia Identity Registry.
| Phase | Name | What it does |
|---|---|---|
| 1 | Guard | Policy enforcement + observability for agent payments (demand side) |
| 2 | Gate | x402 monetization middleware for API vendors (supply side) |
| 3 | Graph | Reputation scoring over agents and vendors (the data moat) |
A complete demand-side Guard loop, runnable two ways: fully offline on mock rails (no accounts, no Docker, no chain), or live on Base Sepolia over the real x402 stack:
以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗