Buyers compare modeled agent work with seller-set evaluation, execution, artifact, and source-license prices. FunctionFoundry’s build ranges, future platform fee, and organization plan remain proposals under validation.
VERSION 1.1.0 / LEDGERWORKS
authorize demo wallet → issue rights → grant entitlement
The current prototype does not charge platform fees. These tiers explain the intended model without presenting a proposed business model as a signed commercial offer.
Free
Search, compare, and inspect public capability evidence before deciding whether to evaluate or buy.
Free
Build and submit a complete capability listing while the product and marketplace economics are being validated.
Contact
A proposed control plane for teams that need central policy, private supply, and procurement support.
The marketplace supports multiple offers per capability version. Buyers see what runs where, what they receive, what they may change, and how the price is measured.
These values are configurable seed fixtures. They are not recommendations, quotes, or evidence of completed third-party sales.
The deterministic ff-build-model-v1 translates a compiled requirement into token, agent-time, tool-call, CI-time, iteration, and human-review ranges. These defaults convert the range into a comparable planning cost.
A configurable blended planning rate across input, cached input, and output—not a provider quote.
A placeholder for hosted agent runtime or orchestration cost, kept separate from human engineering time.
A configurable CI normalization. Tool-specific execution fees remain an explicit future input.
The default loaded review assumption for security, correctness, maintainability, and production acceptance.
Change the engineering assumptions instead of accepting a single savings claim. This separate model compares first-year labor and access costs using the seeded bank-normalizer offers; the agent-compute ranges above are not silently converted into dollars.
All values are directional inputs controlled by the viewer.
Estimated first-year difference from an internal build: $46,551.
Directional prototype model—not a quote. Excludes tax, payment fees, infrastructure, legal review, model tokens, agent runtime, CI/tool charges, risk-adjusted downtime, and production support. Purchased-capability maintenance is modeled as 25% of the entered internal maintenance hours for source and 30% for an artifact.
The proposed model aligns revenue with completed purchases, while sellers retain control of capability pricing. No platform fee is collected by the demo provider today.
Seller-configured fixture offer.
Illustrative; not active or finalized.
Before any payment-provider cost or tax.
Before payment fees, tax, or refunds.
The local DemoPaymentProvider exercises policy, failure, idempotency, settlement, receipt, license, entitlement, and audit behavior without claiming an external transaction occurred.
Balance, per-transaction limit, and daily limit.
Organization, version status, license, and explicit confirmation.
Simulated success or failure with an idempotency key.
License, entitlement, receipt, artifact, and audit event.
No. The local prototype does not collect a platform fee or move external funds. Twelve percent is an illustrative future rate included to test marketplace economics and seller expectations.
The seller configures each offer. A capability version can expose evaluation, hosted execution, deployable artifact, and source-license options with different prices, scopes, rights, and restrictions.
No. They are broad prototype planning assumptions by capability level. The current product does not ingest model-provider bills, coding-agent traces, CI invoices, or completed-project counterfactuals. Recorded license spend stays visibly separate from modeled build economics.
Agent purchases require organization-scoped authentication, explicit confirmation, a per-transaction limit, a daily spending limit, sufficient demo balance, and an idempotency key. Those checks happen on the server.
No. Prototype license records demonstrate explicit rights and entitlement behavior, but their language has not received legal review. Production templates require qualified counsel and jurisdiction-specific terms.
The proposed plan would add private supply, centralized license inventory, organization policy, SSO/provisioning, procurement workflows, and support. Packaging and pricing have not been finalized.
Start with the directional build model, open the seeded commercial-source offer, run its fixture evaluation, authorize the $799 demo-wallet transaction, and inspect the issued license and entitlement.
Ready for review