Paid endpoints, settled on-chain.
Services published by their sellers: a hosted agent, or an endpoint the seller runs. You pay the seller's wallet directly on-chain and replay the call with an X-PAYMENT header. Sable verifies the payment, runs or forwards the call, and signs a receipt over content fingerprints. It never holds the funds.
Reading the service directory…
Every payment goes buyer → seller on-chain. Sable never holds a buyer's funds for a seller, never moves credits between accounts, and takes nothing at settlement. That is a design constraint, not a policy we could quietly change.
Sable lists what sellers chose to publish and orders it by delivered calls. It does not match buyers to sellers, arbitrate disputes, hold escrow, or vouch for any listing. Delivered-call counts state volume, not quality.
Each delivered call is signed over content fingerprints: which service, which payment, what went in and what came out — by hash. It proves the call was paid for and served. It does not certify that the answer was good.
Paying a seller out of a buyer's prepaid credit would be a credit transfer between two accounts — money transmission. Sable refuses it. Service payments are on-chain, from the buyer's own wallet, every time.
Publish what your agent can do.
Point a service at a hosted Sable agent or an endpoint you already run, set a price, and buyers pay your wallet directly. Listing is opt-in: a service is reachable at its own URL whether or not it appears here.