Announcing SOLVENT — an autonomous AI agent that runs as a profitable, self-funding business

[ianalloway]

Hello everyone — excited to announce SOLVENT, an autonomous AI agent designed to run as a profitable, self-funding business.

---

Summary

SOLVENT accepts payments via Stripe, fulfills work using NVIDIA Nemotron, and manages vendor payouts and treasury — so it aims to never operate at a loss. Every job is margin-gated before Stripe is touched, and every vendor spend is screened by a NemoClaw-style policy sandbox before it executes.

Built in Python with no external dependencies required for the demo.

---

Key Features

• Stripe integration — Payment Links with Checkout Session polling and optional webhook verification (checkout.session.completed). Records cs_... and pi_... IDs on the ledger before fulfilment begins.
• Nemotron-backed fulfillment — NVIDIA Llama-3.1-Nemotron-Ultra produces research briefs; falls back to a deterministic offline stub so the demo always works without an API key.
• Treasury & billing policies — enforces a vendor allowlist, per-transaction cap, rolling 24h budget, minimum cash reserve, and no-negative-ROI rule.
• Safety hard-caps — maximum daily spend and minimum reserve enforced before any payment executes; large payouts can be gated behind manual approval rules.
• Audit logs — every cs_... checkout session and pi_... PaymentIntent is recorded on the ledger. Dashboard refreshes live after each job.
• Stripe Issuing — outbound vendor spend uses capped single-use virtual debit cards in test mode.

---

Quickstart

git clone https://github.com/ianalloway/solvent-agent.git
cd solvent-agent
python3 run_demo.py

No install required. The agent runs on offline stubs by default.

To enable live inference and real Stripe test payments:

pip install -r requirements.txt
export NVIDIA_API_KEY=nvapi-...
export STRIPE_API_KEY=sk_test_...
python3 run_demo.py

---

Environment Variables

Variable	Purpose
NVIDIA_API_KEY	Live Nemotron inference
STRIPE_API_KEY	Stripe test key (sk_test_... only — live keys refused)
STRIPE_WEBHOOK_SECRET	Optional webhook verification
STRIPE_PAYMENT_POLL_TIMEOUT	Seconds to wait for payment (default 120)
STRIPE_PAYMENT_POLL_INTERVAL	Poll interval in seconds (default 2)
SOLVENT_FORCE_STRIPE_SIMULATE	Force offline simulate mode even with a key set

---

Demo Results

A typical batch session (3 jobs accepted, 1 declined below margin floor):

Metric	Value
Revenue	$223.00
Operating spend	$13.35
Net profit	$209.65
Margin	94%

---

Security & Safety

• The agent enforces a hard daily spend cap and a minimum cash reserve before any payment executes.
• Outbound payments use Stripe Issuing virtual cards capped to the exact vendor amount.
• The Stripe client refuses live keys (sk_live_...) outright — test mode only.
• Review and test fully in Stripe test mode before considering any production use.

---

Feedback Wanted

• Are the default finance thresholds (margin floor, reserve, per-transaction cap) reasonable for your use case?
• Any additional integration connectors you would like to see — bookkeeping, treasury providers, other payment rails?
• Suggestions for documentation, example workflows, or deployment patterns?

Thanks for taking a look — happy to answer questions.

— @ianalloway