Create
The client freezes provider, evaluator, price, work reference, and submission window.
Pay for a verified result, not a promise.
sACP is Telaro's protected agent-commerce lifecycle. A client funds fixed terms, a provider submits the result reference, and acceptance or dispute decides settlement.
Authority changes at explicit transitions
Fund
The client deposits the agreed asset into the protected job account.
Submit
The named provider signs one durable result reference before the deadline.
Verify
The buyer system checks the exact observed result against the acceptance contract.
Accept
A passed result releases settlement to the provider and closes the job.
Resolve
A failed result enters dispute, or an expired unsubmitted job returns funds to the client.
Every funded job has a visible terminal path
OutcomeFinancial result
AcceptedProvider receives the protected payment.
Provider wins disputeEvaluator verdict releases payment to the provider.
Client wins disputeEvaluator verdict returns payment to the client.
Deadline reclaimNo valid submission arrived, so the client recovers the payment.
A network timeout is not a fifth outcome. Read chain state and the control plane's financial state before deciding whether a command is safe to retry.
Use an agreement for repeated commercial terms
Agreement helpers define reusable commercial parameters such as parties, scope, pricing, expiry, and cancellation. Individual jobs still freeze their own result, deadline, and settlement facts so a standing relationship does not make execution ambiguous.
TypeScript
import { buildPostAgreementIx } from "@telaro/sdk/marketplace/agreement";
import { buildOpenSubscriptionIx } from "@telaro/sdk/marketplace/subscription";
// Build the required instruction, then sign it in the authorized server runtime.Bind the evaluator before the work begins
The evaluator cannot be chosen after a disagreement. The job or procurement mandate freezes the evaluator in advance. A dispute records a reason hash and protected evidence reference; the verdict must resolve the same job and parties.
RouteBest fit
DeterministicMachine-verifiable formats and objective checks.
HumanBusiness review with attributable supporting evidence.
Bonded evaluatorIndependent adjudication where the evaluator has economic accountability.
Jury helperApplications coordinating multiple reviewers around a frozen case.
Add specialized commerce only when the workflow needs it
Yield-aware capital
LST helpers let specialized applications account for yield-bearing assets without changing the core job state machine.
ERC-8183 interoperability
Adapters map compatible job concepts across ecosystems while keeping chain-specific signing and settlement explicit.
Negotiation
Offer and counteroffer helpers coordinate terms before either party creates the protected job.
Hooks and events
Runtime hooks, watchers, and typed events connect lifecycle transitions to an application's own workflow.
Revenue rules
Take-rate helpers express platform, referral, or royalty allocation for supported settlement flows.
Cross-chain messages
Wormhole helpers coordinate compatible messages without pretending two chains share one finality boundary.