Agent Operator Library
Structured prompts and workflows for repeatable AI-assisted tasks. Use the patterns as-is or adapt them to your own operating rhythm.
CROSSINGKEY AGENT DOCK
A professional station for human and machine agents: buy a starting capability, connect your own API, set the boundary, and move a reviewed result into the work that matters.
Dock a real task, define the operating context, and choose the right capability. The product brings the operating logic; you bring the resource and the judgment.
State the task, source material, desired result, and what must remain human.
Connect the API, choose the model, and set approvals before a run.
Review the trace, keep the result, and move it into your real workflow.
Ready-to-use packages for the dock. Custom agent work when the task needs your systems, data, or rules.
Structured prompts and workflows for repeatable AI-assisted tasks. Use the patterns as-is or adapt them to your own operating rhythm.
A practical guide to private, offline AI workflows for creators and small teams that want more control over their context.
Editable planning and operating templates that give an agent better inputs and give the reviewer a clearer frame.
Machine-readable discovery, evaluation, payment, receipts, and bounded capabilities for agents that need a real service behind the interface.
Bring the task, tools, and approval boundary. We scope the smallest useful system and define what “done” means before implementation.
Agent capabilities that can be inspected, priced, tested, and called through the CrossingKey machine interface.
Connect the Agent Dock backend to load live capability metadata, pricing, permissions, and MCP tool bindings.
This buyer workbench supports OpenAI, Anthropic, and OpenAI-compatible endpoints. Your key stays in memory for this session and is sent only to the provider you choose; it is not stored by CrossingKey.
Configure a provider, choose an agent template, and run a session. The output will appear here with a lightweight trace.
The station is designed around buyer-owned context and explicit control. It can help you think, transform, review, and prepare; it does not silently publish, spend, or change an external system.
Runs produce an answer and trace before any action is considered.
You connect the provider and choose the model. CrossingKey does not ask for your account password.
Outputs are drafts until you approve, edit, or deliver them yourself.
Each useful run should leave enough context for someone else to understand the result.
Choose a package from the sales collection, connect the API you already control, and use the agent inside your own workflow. Custom work starts with a scoped brief and a clear launch boundary.
Send the task, the systems involved, and the boundary that must stay human.