Introduction - Patchwork

Patchwork has two doors. Most teams start with Loom: register a connection, wrap your endpoints as patches, and embed an agent that calls your backend as the signed-in user. The other door is the workbench — standalone REST products you call with an API key and no agent at all.

Embed an agent

Direct or relay. Your tools and ours, one runtime.

Call identify

Resolve an account or wallet in one request. Live today.

Two doors

Loom is the product we sell. You build an agent; your users meet an assistant. We run the loop, the guardrails, and the traces. You keep the keys, the brand, and the money. Workbench is the catalog. Each tool is a plain REST call. The first one is POST /v1/identify. fx-rates, extract, and vision are next. Call them from your code, or wire them into an agent as a patch when that binding ships. A patch is not a bare API. A tool is not an agent. An agent is not an assistant until you ship it.

Base URL

All public requests go to https://api.usepatchwork.co. The API speaks JSON over HTTPS. Responses are wrapped in a status envelope — see Errors.

curl https://api.usepatchwork.co/v1/identify \
  -H "Authorization: Bearer $PATCHWORK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"rail":"routing_number","code":"021000021"}'

Promo credits cover your first calls. There is no complimentary test lane.

Where to go next

Get a key

Create a workspace and copy a secret key from Developers. See Authentication.

Pick a door

Identify an account, or embed an agent.

Read the reference

Every public endpoint, grouped by product, lives under API Reference.

⌘I

Embed an agent

Call identify

​Two doors

​Base URL

​Where to go next

Two doors

Base URL

Where to go next