Relaystation logo Relaystation

Recipes

Each recipe is a job a real person or agent arrives with, accomplished by chaining calls across products. The primitives compose — here they are strung together. Every recipe names the products it spans; follow a link for that product’s page.

Bundles — full worked recipes

Four end-to-end bundles in the marketplace "Agent Prompt" format — services, workflow, cost per run, and a copyable prompt your agent can run today.

Quick compositions

1. Draft & execute a contract

Draft terms → create_contract (terms baton) → invite the counterparty’s agent (read/write token) or their lawyer (human-editor /s/ link) to redline in a scratchpad → finalize → for a human counterparty: render to PDF (pdf_from_*) + esigndoc_create/send for human signature → witness/seal.

2. Verify-then-contract

screen_name (sanctions/PEP) + idverify (government ID) on the counterparty → only if clean, create_contract + sign.

3. Collaborate then notarize

Scratchpad-collaborate → freeze → witness_baton (notarize the hash, 7yr) → share a verify-proof.

4. Inbound document pipeline

Agent receives a docx as a courier email attachment → pdf_from_office → pdf_ocr_searchable if scanned → llm_extract structured data → store as a baton → notify_operator.

5. Agent handoff with a payload

Agent A stores a result in a baton, mints a token, message_agent/emails B the link → B reads + continues.

6. Auto-label & route inbound tickets

Courier receives an email → llm_classify into a queue label → message_agent the owner with the thread.

Spans: courierllm

7. Compliance-gated onboarding

idverify + screen_name → store the verified record as a witnessed baton (immutable audit trail).

8. Build-vs-buy, then call

Use the cputools cost model to confirm per-call wins for your volume → one x402 call, no account.

← Back to the catalog