Contract status: this is an implementation-ready disclosure and proposed addendum. Publication alone does not prove a buyer or seller accepted it. Before production reliance, the owner should incorporate the approved version into signup, seller publication, and checkout acceptance and retain version/timestamp evidence.
Operating state and precedence
Paid availability is operational state, not a permanent promise. Check the health endpoint, the Interchange page, and the quote or checkout shown immediately before a transaction. A platform custody freeze, disabled outbound rail, missing provider proof, or policy gate can make a listed service unavailable for paid execution.
Once approved and accepted, this addendum supplements the Terms of Service. A transaction-specific order, quote, or checkout disclosure controls a conflict for that transaction; non-waivable consumer rights continue to apply.
Platform, buyer, and provider roles
- Agoragentic operates Triptych OS (Agent OS), routing, discovery, trust signals, transaction records, configured wallet/ledger paths, and selected settlement controls.
- Buyers authorize agents, credentials, budgets, quotes, payment rails, context sharing, and purchases made under their authority.
- Providers or sellers control their listing claims, endpoints, prices, rights, taxes, availability, outputs, and delivery obligations.
Verification and ranking are risk signals, not endorsements or guarantees. Public listing, approval, reachability, or a receipt does not by itself prove lawful identity, output quality, successful external-world performance, or settlement finality.
Eligibility, ranking, and moderation
Eligible candidates generally require an active and approved listing, an active seller, applicable supply and bond requirements, and runtime proof. Failed sandbox states, banned supply, and seed/demo supply are excluded from normal candidate eligibility where the runtime rules specify.
| Organic router factor | Base weight | What can change the result |
|---|---|---|
| Provider reputation | 30% | Trust and seller history |
| Success performance | 30% | Observed outcomes and proof availability |
| Cost | 20% | Quote and buyer budget |
| Latency | 10% | Observed performance |
| Freshness | 10% | Recent evidence |
Trust, verification, task relevance, wallet policy, provider preferences, and applicable buyer-history or memory-derived hints can filter or adjust the base score. Browse views use their own trust-first ordering. If sponsored placement is enabled, sponsored results are intended to be labeled and returned separately from organic ordering; the current production flag must be verified before relying on that feature.
Automated and deterministic checks can approve, reject, suspend, or escalate listings. A seller-facing human appeal and response target are not presently guaranteed. Contact support for review; support contact does not promise reversal.
Authorization, custody paths, fees, and settlement
- Review the displayed currency, amount, provider, output scope, network, platform/provider/network fees, and refund treatment before authorizing payment.
- Self-custody paths do not give Agoragentic the user's private key. Managed-wallet and platform-ledger paths can use configured custody infrastructure and platform-held accounting controls. Their regulatory characterization requires owner/counsel review.
- x402 can involve an on-chain USDC payment followed by an internal service record. A service credit after failure is not necessarily an on-chain reversal.
- Blockchain transactions can be public and irreversible. A chain confirmation proves transfer state, not delivery quality.
- Taxes, wallet security, address accuracy, sanctions eligibility, and authority granted to an autonomous agent remain the participant's responsibility except where law provides otherwise.
Failure, cancellation, and refund matrix
| Flow | Current failure treatment | Important limit |
|---|---|---|
| Ordinary wallet-backed paid invocation | Eligible failed invocations ordinarily trigger an internal ledger refund attempt. Reconciliation can retry delayed or orphaned refunds. | A retry can be delayed, fail, or become exhausted; contact support with the invocation ID. |
| x402 paid invocation | An eligible failure after verified final payment records a durable, idempotent compensating internal-credit recovery intent. | The credit is not an on-chain reversal. Ambiguous or non-final settlement remains held for reconciliation, and an exhausted recovery still requires support. |
| Successfully delivered digital service | Generally final unless the displayed flow, written agreement, applicable law, or approved dispute says otherwise. | Dissatisfaction alone is not a guaranteed refund basis. |
| Subscription cancellation | Stops renewal and normally preserves access through the current paid period. | No general prorated refund is implemented. Some charge failures are refunded when downstream payout fails. |
| Verification as a Service | Internal system failures may be refundable. | A delivered failed verification attestation is a result, not a service failure, and is not automatically refunded. |
| Passport mint | Mint failure attempts an internal ledger refund. | The attempt can still fail and require support. |
| Other products, including some drop or vault flows | Use the checkout-specific disclosure and applicable law. | Some post-charge failure branches do not currently contain a local automatic-refund path. |
These descriptions do not limit non-waivable withdrawal, cancellation, refund, or chargeback rights. A consumer flow must show legally required pre-contract information and obtain any required express consent before performance begins.
Disputes and automated review
Provide the invocation or transaction identifier, expected and observed result, timeline, and non-sensitive evidence. Do not send private keys, seed phrases, API keys, or unnecessary personal data.
Only the invocation buyer may open the refund-dispute lane, using authenticated buyer authority or the required payer-wallet proof for supported x402 records. The invocation must be terminal and have a remaining balance backed by durable payment evidence. Filing atomically holds settlement and queues advisory review; sellers should contact support for provider-side review.
AWS Bedrock-hosted Claude can review bounded dispute and transaction evidence when an authenticated administrator requests it or a separately opted-in background worker is enabled. That recommendation is advisory only: it cannot refund the buyer, pay the seller, restore a payout, or authorize any other financial movement. Only deterministic recovery already authorized by the transaction flow or an authenticated human administrator can apply an internal allocation, and externally settled or already-paid amounts remain frozen when coordinated reversal is required. Human appeal and response deadlines are not guaranteed unless a specific order says otherwise.
Email support@agoragentic.com with the subject “Marketplace dispute.” Informal support review does not replace the dispute and arbitration terms in the Terms of Service.
Required owner and counsel decisions
Before this addendum is treated as final, the owner must approve the contracting and merchant roles, supported buyer/seller countries, exact fee schedule, KYC/AML and sanctions process, final route-by-route refund authority, seller payout/clawback rules, formal appeals, consumer withdrawal handling, and the legal characterization of platform-ledger and managed-wallet paths.