Built for what Algorand doesn't have yet.
Fast finality and low fixed fees make Algorand a good settlement layer for agentic micropayments. Three things a real product still needed didn't exist, so Veldar built them.
No native pay-per-call HTTP payments
x402 (docs.x402.org) defines an HTTP-native flow: a client requests a resource, the server replies 402 Payment Required with payment terms, the client pays, and the server verifies and serves the resource once settlement is confirmed. It's a clean fit for Algorand's low fixed fees and fast finality, but no standard implementation exists for the network. Veldar's facilitator (website/lib/facilitator.ts) fills that gap: it verifies a submitted payment payload against a confirmed Algorand TestNet transaction via algosdk, supports both the exact scheme (fixed price per call) and the upto scheme (usage-based, settle actual amount used), and issues an idempotent receipt so a retried request can't double-settle. Any HTTP API, including Veldar's own marketplace providers, can sit behind it and become pay-per-call.
No orchestration layer for agents
A smart contract can settle a payment instantly, but it has no opinion about whether that payment should happen yet, whether the result it's paying for was actually delivered, or what to do when a step fails halfway through a multi-provider workflow. Veldar's orchestrator (website/lib/orchestrator.ts) is that missing layer: it compiles a goal into a step graph with dependencies and conditions, quotes each step against the live marketplace, checks it against the user's subscription-tier budget cap before ever reserving spend, and opens a human-in-the-loop approval whenever a step exceeds that cap or targets an unverified provider. Every offer, quote, approval, payment, and verification result is written to an append-only ledger, so a workflow can be replayed and audited after the fact, not just trusted in the moment.
No consumer-facing agent UX
algosdk and AlgoKit are excellent developer tools, but neither one answers the question a normal user actually has: "is it safe to let this thing spend my money while I'm not watching?" Veldar's app and dashboard translate every technical event into something a non-technical person can act on: a plain-language approval card instead of a raw transaction payload, a running spend total against a visible budget instead of a wallet balance, and a full replayable trace instead of a block explorer link. The wallet and the contract stay exactly where they belong, underneath the interface, not in front of it.
Safety boundaries, not an afterthought.
- Every payment in this build settles on Algorand TestNet. No production wallets, no real funds.
- The facilitator's Algorand account is scoped to settlement only; it never holds custody of user funds beyond a single verification step.
- Budget caps are enforced by the orchestrator's policy engine, server-side, regardless of what a client displays.
- A workflow can be cancelled mid-run at any point; the ledger records exactly what was delivered and what wasn't purchased.