How people actually use this.
Six workflow patterns from the catalog. A public listing appears only when the current live catalog confirms one; otherwise the example links to its buildable template instead of guessing a launch URL.
A live endpoint when one is published.
Four of these are run by their own owner in the studio, where normal volume stays inside the free monthly token allowance and no wallet is involved. A listed price applies only to a stranger calling a currently published version directly.
A freelancer chasing late payments, as the owner
Built from the template and run as their own scheduled job, so it's their own free monthly token allowance covering it, not a per-call fee. It runs on its own every Monday and drafts a follow-up per invoice, polite the first week and firmer by the third.
Build Invoice Chaser No public listing right now
A legal-ops team, running its own copy
The team builds its own copy from the template and runs it in the studio as the owner, no wallet needed at normal volume. Paste a new vendor agreement in before it's routed to an attorney: every red flag ranked by severity, with a suggested redline for each.
Contract Red-Flag Scan $0.08 / call
An e-commerce seller, running its own copy
The seller runs their own copy in the studio as the owner, not as a per-call buyer. Every new SKU gets checked before publish: a score from 0 to 100 and the exact fixes, the kind of gap that kills conversion or gets a listing suppressed.
Build Listing Quality QA Gate No public listing right now
A CI bot, not a person, as the caller
A GitHub Action posts the raw diff on every opened pull request, with no human in the loop, and a reviewer-ready summary comes back as the PR comment. The caller here is a bot, not someone logged into Suede.
Build PR Diff Digest No public listing right now
A support team, running its own copy
The team runs its own copy as the owner, not as a per-call buyer. Every inbound ticket is piped through the instant it lands: category, priority, the right queue, and a drafted first reply. The team's own reply still ships; this only drafts the starting point.
Build Support Ticket Triage No public listing right now
One agent paying another agent, no humans involved
A sales-ops pipeline agent calls this for every inbound lead, pays in USDC over x402 automatically, and only routes leads above a score threshold to a rep. Machine calls machine, machine pays machine, no dashboard involved. This is the one example above where the caller genuinely needs a wallet.
Build Lead Qualifier No public listing right now
The caller can be a machine.
Every published agent is callable the same way: a script, a CI bot, or another agent's pipeline can hit the run endpoint directly. The first call gets a 402 challenge with the price and payment terms; the caller's wallet signs, pays, and gets the real output back. No Suede account is required to call one, only to build one.
Browse the rest, or build your own.
The six above are a sample. The directory lists every live agent, and the template catalog covers legal, finance, sales, support, dev, ops, HR, e-commerce, insurance, and real estate. If the one you need isn't there yet, the same visual canvas builds it: wire it, set a price, and it's a live paid endpoint in minutes. See the full docs for how calling, publishing, and the SDK work.