Where user can Ideate , build , own , monitize web3 agents via deploying agent Onchain.
Valdyum is solving Automation On-chain. An Agentic AI Infrastructure where user can ideate, build, own , monitize via deploying agent Onchain . Become the Righter owner of your agents credibility & ownership , Monetization . Along with Developers toolkit to build and use thier agents in thier own dapp/project with better deployment environment locally with CLI and executing AI agents with verifiable payment rails on Stellar.
5+ active users with their Name, Wallet ID, email and Feedback: https://docs.google.com/spreadsheets/d/1vLztvp1yzuMoxyTsJxFebRteebIhMIdvP6aaxCJ9CrQ/edit?usp=drivesdk
Full architecture document: docs/architecture/ARCHITECTURE.md
It combines:
- Soroban contracts for on-chain registry and deployment validation
- HTTP 0x402 protocol to AI - AI, pay-per-request execution in XLM
- Wallet-signature UX with Multiwallet auth
- Realtime pub/sub pipeline for events and analytics
- Agent marketplace, fork economy, workflow executor, and trading surface
Primary proof transaction (Tx / payment):
- My freighter wallet address : GARN7A6OJKPR3HAPVIKM6GRUD7KMEHYQ76VJJCO4AAKQ6ETEKFQPQ24T
- Agent VALIDATOR ID= CAFDQPT6PUWS343TRAAX5O5PCKR5G5YPWBXUDP34NC745XJKAENI4GVY (Deployed On-chain) Validation Fee: 5 XLM
- AgentRegistry CONTRACT ID= CA3W37NQUHMFYJJD3TW4B2DI5ABKH7M7BNAMQISB5VW3BCYNO2PC2MYY (Deployed On-chain)
- Tx ID:
0367f4f328678305d283ed8fc7b71866df5f0523e7efa3ef00bb3abc2b77e541 - Explorer: https://stellar.expert/explorer/testnet/tx/0367f4f328678305d283ed8fc7b71866df5f0523e7efa3ef00bb3abc2b77e541
- Status: successful
- Memo observed:
fork:d211defa-57a7-4f41-b08d - Amount observed:
0.1 XLM - Fee charged:
0.00001 XLM
- fork-wallet-confirm.png
2. stellar-explorer-proof.png
3. marketplace-fork-success.png
4. run-payment-modal.png
5. run-summary-live-feed.png
6. build-validation-sign.png
7. trading-surface.png
8. workflow-waiting-signature.png
9. workflow-invoice-confirmed.png
10. dashboard-analytics.png
After adding images, commit and push. The main README references these paths directly.
AI agents are easy to build but hard to monetize safely across open networks. Traditional API keys and off-chain billing create trust gaps:
- No atomic link between payment and execution
- No shared payment standard between autonomous clients
- No transparent, verifiable evidence that value moved
Valdyum addresses this by pairing 0x402 style payment negotiation with Stellar transactions and on-chain policy enforcement.
Stellar is a strong fit for machine-to-machine micro-payments and agent marketplaces:
- Fast finality and low fees for frequent small-value API calls
- Mature account model and strong wallet ecosystem (Freighter)
- Great UX for memo-tagged payments, which map naturally to request IDs
- Soroban smart contracts for deterministic validation and inter-contract control
- Publicly verifiable transaction proofs through Horizon / Explorer
- Build custom agents with model, prompt, tools, visibility, and pricing
- Register agents with validator + registry contract flow
- Run agents through a 402 payment challenge-response mechanism
- Fork marketplace agents with paid fork transactions
- Execute paid workflow tasks with invoices and explorer proofs
- Track activity in dashboard and live feed components
flowchart LR
U[User + Freighter Wallet] --> FE[Next.js App Router UI]
FE --> API[API Routes / Server Actions]
API --> SUPA[(Supabase)]
API --> AI[OpenAI + Anthropic]
API --> HZ[Stellar Horizon]
API --> VAL[AgentValidator Contract]
VAL -->|invoke_contract| REG[AgentRegistry Contract]
API --> ABLY[Ably Realtime]
API --> Q[QStash Consumers]
Q --> SUPA
ABLY --> FE
- User opens the app and connects Freighter (or other supported wallet).
- Public key is stored locally for session-scoped UX and request signing context.
- User configures agent metadata (name/model/prompt/price/visibility/tools).
POST /api/agents/validate-deploybuilds a Soroban validation transaction (XDR).- User signs in wallet.
POST /api/agents/confirm-deploysubmits and prepares confirmation call.- Validator contract confirms and performs inter-contract call to registry.
- Agent metadata is persisted to Supabase for app indexing and search.
- Public agents appear in marketplace cards.
- Consumer can fork an existing agent by paying fork fee in XLM.
- Memo ties payment to fork action (
fork:<agent-or-request-id>). - Forked configuration can be customized before first execution.
- Client calls
POST /api/agents/[id]/runwith prompt input. - If unpaid, server returns payment challenge (402 semantics + payment details).
- Wallet signs and submits Stellar payment.
- Client retries with tx hash and wallet headers.
- Server verifies payment via Horizon and executes selected model.
- Request, billing, and runtime stats are persisted.
- Trading page simulates strategy actions with XLM-centric UX.
- Workflow page batches paid task executions and wallet approvals.
- Invoice card records amount, tx hash, payer, timestamp, and explorer link.
- Realtime events stream through Ably/QStash pipeline.
- Dashboard aggregates request counts, billing, and latency surfaces.
- Explorer links provide independent payment proof.
- Validates deploy intent and confirmation signatures
- Manages pending deployment state
- Performs inter-contract call into registry during confirmation
- Canonical on-chain index for registered agents
- Holds pricing/ownership metadata and request accounting hooks
- Serves as the source of truth for validator cross-contract checks
Client -> validate-deploy API -> sign tx -> confirm-deploy API
-> AgentValidator.confirm_deploy(...)
-> invoke_contract(AgentRegistry.register_agent(...))
-> on-chain registration success
- Freighter fork confirmation proves user-signed payment authorization before marketplace fork completes.
- Stellar Expert receipt confirms fork tx finality, ledger inclusion, memo integrity, and signature validity.
- Marketplace success banner shows app-level acknowledgment wired to confirmed chain payment.
- Run-agent payment modal demonstrates 402 challenge-response UX tied to wallet signature.
- Agent run summary shows billed amount and runtime metadata linked to the paid execution path.
- Build step validation modal proves deploy flow requires explicit wallet approval before contract submission.
- Confirm-deploy warning state highlights guarded confirmation path for potentially failing preconditions.
- Trading surface demonstrates XLM-focused strategy execution context integrated with wallet identity.
- Workflow executor waiting state proves asynchronous task orchestration blocked on wallet payment signature.
- Workflow invoice panel provides structured proof payload: tx hash, payer, amount, timestamp, explorer link.
- Dashboard panels aggregate monetization telemetry and request analytics after protocol interactions.
POST /api/agents/createGET /api/agents/listGET /api/agents/[id]POST /api/agents/[id]/runPOST /api/agents/validate-deployPOST /api/agents/confirm-deployPOST /api/agents/submit-confirmationPOST /api/payment/verifyGET /api/dashboard/analyticsGET /api/dashboard/requestsGET /api/ably/token
- Node.js 18+
- pnpm 10+
- Freighter wallet (for end-to-end payment/deploy tests)
- Supabase project (recommended for full mode)
pnpm installCreate local env and fill your own keys (never commit secrets):
cp .env.example .env.localpnpm run devpnpm run lint
pnpm exec tsc --noEmit
pnpm run buildWorkflow file: .github/workflows/ci.yml
lint-and-type-check: ESLint CLI + TypeScript noEmitbuild: Next production build + artifact uploaddocker-build: Docker buildx image build (no push)
This pipeline ensures code quality, type safety, production build integrity, and deploy parity.
.env.localand.env.local.bakare ignored and must remain local only.- Never commit API keys, private keys, or service-role secrets.
- If a key is ever exposed, rotate it immediately.
Valdyum demonstrates that autonomous software can be monetized transparently when identity, payment, and execution are composed as one protocol surface.
By building on Stellar, the project converts abstract AI usage into verifiable economic events that users, builders, and integrators can trust.