Every paid request
walks the same seven steps.
AIaaS bundles, procurement bids, stemcell purchases, custom aegents, Nucolai tenant onboarding — they all flow through the same parse-score-quote-route-execute-settle-support pipeline. The orchestrator is called billybin. The mechanics are below.
The pipeline
Each step has a single responsibility and a single output. Most steps are implemented as composable biniz — small, testable units of intellectual property. New channels plug into the same flow.
-
01
requirement parse
Incoming request — RFP text, AIaaS terminal input, tender document, mail enquiry — is parsed into structured requirements: scope, constraints, acceptance criteria, deadline, deliverable shape.
- Service: function-identifier (port 7352)
- Output: structured requirement object
-
02
coverage analysis
Each requirement is scored against the biniz catalog and the aegent fleet. The result is a coverage map: which parts of the request are already solved, which need a new biniz, which need custom work, and what each delta costs.
- Service: biniz-coverage-analyzer (port 7354)
- Output: coverage map + gap-cost estimate
-
03
quote build
The coverage map turns into a format-aware quote artifact — a bundle invoice for AIaaS, a bid document for procurement, a tenant proposal for Nucolai. Each line item maps to a real cost (fuelcost + biniz license + work + margin).
- Service: quote-builder (port 7356)
- Output: signed quote artifact in the request's format
-
04
payment-rail route
Based on the customer profile (jurisdiction, KYC stance, preferred currency), the right payment rail is selected: Lightning, on-chain BTC, Monero, fiat invoice with net-30, or a wire instruction. The corresponding payment instrument is emitted.
- Service: payment-rail-router (port 7353)
- Output: BOLT-11 invoice / address / IBAN / etc.
-
05
execute
On payment settlement, the build dispatcher fires the appropriate workflow: AIaaS build job, AEDLnet stemcell spawn, tender bid auto-draft, aegent provisioning, etc. Work happens against the agreed benchmark.
- Service: broker (port 7700) + worker fleet
- Output: deliverable matching the benchmark
-
06
settle
The benchmark is evaluated. If it passes, the deliverable is released and the run is marked settled. If it fails, the product-price portion is refunded (fuelcost is non-refundable per the bundle-invoice model); a "best attempt" is delivered as proof-of-effort.
- Service: moneylog (port 7355) — source of truth
- Output: settled / refunded / disputed state
-
07
support
Post-delivery: response to bug reports against the benchmark, renewal notifications for hosted services, stemcell koma-watch + revival prompts, and minor scope-tightening within the original contract.
- Channel: oden@on1.uno
- SLA: 48 h Stockholm time
What triggers the pipeline
Every public service in the catalog routes into the same flow. The first step (parse) is channel-aware so each surface gets its own UX while the rest of the pipeline stays uniform.
Terminal at /aiaas — describe → benchmark → bundle → pay.
Tier picker at /g82aedl — pick a stemcell, sign the contract, pay the deposit.
Whitelist-only overflow — read the explainer, apply by mail.
Tenant enquiry at /nrs — tenant scope → corpus quote → onboarding.
Per-seat request at /meetass — seat count + integration → invoice.
Retainer enquiry at /tendern0d — capability profile → drafting volume → fee.
Scoping call — /aegents — purpose → biniz coverage → quote.
Per-biniz licence at /biniz — pick the unit, agree the deployment scope, settle.
Why this matters
Benchmark-contracted
Acceptance criteria are written down before any work starts. You see them. You can change them. They are the contract.
Refund-anchored
If we miss the benchmark, the product portion refunds. The non-refundable portion only covers our actual cost (compute, time-on-task, hosting). Audit trail in moneylog.
Composable
Most work is composed from existing biniz. New work that becomes reusable becomes a biniz too. Same library every customer benefits from.
Rail-agnostic
Sats, EUR, USD, XMR — paid through the same router. No vendor lock-in to any one currency or payment provider.
Send a request
Quote requests, scoping calls, whitelist applications, support — one address handles all of it. Subject line should include the service name so we route to the right pipeline channel.
oden@on1.unoResponse within 48 hours Stockholm time.