Veyra

Veyra decides. Circle pays.

Before an agent spends USDC, Veyra decides whether it should pay, whom, and how much.

Circle gives an agent a wallet, a marketplace, and a way to pay. Veyra is the independent layer in front of that: it measures the evidence available about a counterparty, ranks the alternatives, enforces budget and risk policy, and issues a signed authorization bound to one endpoint and one amount. After execution, the observed outcome becomes new reputation on Arc.

ERC-8004 · ERC-8183 · x402 · Gateway Nanopayments · USDC · Arc

Live — agent-commerce-six.vercel.app · Create an agent, the front door — a personal agent, its brief, and what it has earned on Arc · Choose and pay yourself, the same decision driven by hand · Decision log, every trust-routed action, authorization and onchain settlement as it happened

On Arc mainnet Veyra is ERC-8004 agent #298. It sells its Trust API there, paid through Circle Gateway. Its own contracts (the Trust Gate, the evaluator and the proof registry) stay on Arc Testnet until they are audited.

The agent in front of it

The front door creates Nova, a personal agent owned by the person who made it. Nova starts from an owner-stated goal, interests, and a short owner-confirmed account of where the work already is. It reads official publications and release notes, explains significant changes against what has already been built, with source excerpts, and keeps ordinary commit counts and API listings in background history. Nova may propose a change to that project context and can never confirm one itself. Public-source analysis uses the app's model without charging the owner's wallet.

GOAL       a concrete result the owner wants
  ↓
STATE      what is already true about the work, confirmed by the owner
  ↓
OBSERVE    official publications · release notes · payment changes
  ↓
EXPLAIN    what changed · why it matters against work already done ·
           next step · source excerpts
  ↓
FEEDBACK   was this result useful?
  ↓ only for a specific unanswered question
PROPOSE    suitable tool · expected result · exact price · Veyra policy
  ↓ only after owner approval and existing execution checks
SIGN → EXECUTE → VERIFY → RECEIPT / ARC ATTESTATION

Ask Nova. The owner can put a question to Nova directly.

• Nova answers from Arc's and Circle's documentation first, at no charge.
• Only when that does not answer does it choose a tool on Arc for the question, and price it for the owner to approve.

The brief reads Arc first and Base after, with one card per endpoint. The cards come from Circle's catalogue and from the ERC-8004 registry on Arc.

A missing answer is a research hypothesis, not permission to spend. Financial permission remains Veyra's separate deterministic decision. The owner signs every payment, because autonomous spending is frozen.

Nova never holds money and there is no signing path in its code. It can want to spend and it says so, with a price and a verdict on the item; the payment goes through the same selection, clearance and wallet signature as any other Veyra purchase.

An identity is earned, not granted. The rule is a verified purchase and an attestation somebody else can read — not because Arc re-checks Veyra's verdict (it does not; the verdict stays Veyra's) but because a claim that lives only in Veyra's database is a claim whose only witness is the party making it.

The decision underneath

INTENT     "Research the latest developments in Ambient"
           budget 0.10 USDC · optimize for trust
              ↓
DISCOVER   ERC-8004 agents on Arc  ·  Circle x402 marketplace        4 candidates
              ↓
VERIFY     live endpoint probe · catalog drift · latency
           settlement history · onchain identity      evidence coverage caps the tier
              ↓
DECIDE     ALLOW · ALLOW_WITH_LIMITS · REQUIRE_EVALUATOR · REVIEW · DENY
                                                       fails closed, never silently
              ↓                EIP-712 clearance, bound to endpoint + amount
EXECUTE    x402 / Gateway Nanopayments  ·  ERC-8183 escrow on Arc
              ↓
LEARN      observed outcome → reputation on Arc

One decision core. Two ways to spend. Every score traceable to the evidence that produced it.

Autonomy is frozen

Nova proposes, and the owner signs every payment. On 26 September autonomous spending was frozen for every user:

• AUTONOMY_FROZEN is a constant in lib/execution/autonomy-freeze.ts, not a setting, so no environment variable can undo it.
• The autopilot route answers 503, and new AUTOPILOT mandates are refused.
• The scheduled shadow pass stops before it reads a mandate.

This is the beginning of the README. Read the rest at the original. Read the full README ↗