Robot Marketplace builder guide

Build the robot once. Sell the roofing workflow many times.

This is the public explanation builders can hand to teammates, partners, or buyers. It explains how to package a Contractorfy workflow, what APIs exist, how BYO OpenClaw fits, and why the marketplace can become a distribution channel instead of just an internal tooling shelf.

Builder steps

4

concrete stages from idea to sale

Public route groups

8

documented API families behind the robots

Listed endpoints

129

route paths called out on this page

Product packaging visual

What a sellable robot actually contains

1

Workflow brain

Prompt, reasoning style, and operational outcome.

2

API surface

The routes it calls for jobs, tasks, documents, or Codex traffic.

3

Plan and entitlement

The pricing story and the access checks attached to the install.

4

Tenant-safe auth

Workspace-scoped API keys, OAuth, and runtime scope checks.

5

Public listing

The buyer-facing explanation of what the robot replaces or accelerates.

Builder sequence

The public builder motion from workflow to revenue

I

Pick a roofing problem with repeat demand

Good marketplace robots solve a real, recurring operator pain: supplements, storm follow-up, collections, measurement coordination, document generation, or outbound claim communication.

II

Choose the surface area

Decide whether the robot is mostly a model proxy workflow, a job/task/document workflow, a communications workflow, or a marketplace commerce workflow.

III

Write the listing like a product, not an internal note

Buyers need to know the outcome, the role it replaces, the approval gates, and the APIs it uses. The listing should sell the operational result, not just the underlying model.

IV

Launch, verify, and sell

Publish the listing, verify install and entitlement checks, then point roofing companies to the public marketplace page instead of requiring a sales demo just to understand the product.

BYO OpenClaw lane

The exact external-safe routes builders should care about first

If you already run OpenClaw yourself, start with the routes below. They let your runtime call Contractorfy over HTTPS while Contractorfy keeps the workspace-scoped Codex OAuth and tenant context safe.

GET/api/keys

Workspace API key management

Create and manage the Contractorfy API keys that your external OpenClaw runtime will use.

GET/api/skills/contractorfy/codex/status

External-safe Codex status

Check whether a workspace-scoped Codex OAuth account exists before you send model traffic.

GET/api/skills/contractorfy/codex/models

External-safe Codex model catalog

Ask Contractorfy which model ids are valid for the workspace before your external OpenClaw chooses one.

POST/api/skills/contractorfy/codex/responses

External-safe model execution

Send model requests through Contractorfy while Contractorfy keeps the workspace Codex OAuth credential private.

GET/api/skills/contractorfy/home

Homepage operations wrapper

Fetch the operator home payload so an external robot can reason over jobs, queues, and daily workload without scraping UI.

GET/api/skills/contractorfy/home/overview

Overview wrapper

Read the home overview card data for a workspace or group in a robot-friendly contract.

GET/api/skills/contractorfy/home/queues

Queue wrapper

Read the task and workflow queues that matter to operators right now.

GET/api/skills/contractorfy/home/job-build-calendar

Calendar wrapper

Load build-calendar data from the same route family used by the web homepage.

POST/api/skills/contractorfy/task-extract

Task extraction wrapper

Turn call notes, transcript text, or external automation output into Contractorfy tasks without dropping into the UI first.

Full API catalog

Every Contractorfy API family currently called out for Robot Marketplace

This is the detailed route listing behind the public product story. It is grouped by operational surface so builders can see which lane their robot belongs to and which routes a buyer will ultimately rely on.

Internal operators and AI-assisted workflows

Assistant, research, and Codex sign-in

These routes power the assistant surfaces, job assistant flows, and Codex sign-in bootstrap used by the app.

Ask assistant questionsRun job-level chat workflowsStart or poll Codex sign-in
8 routesCookie session, Supabase bearer, or route-specific auth
/api/assistant/chat/api/assistant/query/api/assistant/search/api/assistant/strategy/api/job-assistant/chat/api/auth/codex/import/api/auth/codex/poll/api/auth/codex/start

Marketplace robots, BYO OpenClaw flows, and operator dashboards

Home dashboards, queues, and task extraction

This is the heart of the operational layer: home payloads, queue views, and task creation and extraction workflows.

Read homepage operational stateExtract tasks from transcript textCreate, assign, route, and execute work
16 routesRead or write scopes depending on route family
/api/home/api/home/job-build-calendar/api/home/overview/api/home/queues/api/skills/contractorfy/home/api/skills/contractorfy/home/job-build-calendar/api/skills/contractorfy/home/overview/api/skills/contractorfy/home/queues/api/skills/contractorfy/task-extract/api/tasks/[taskId]/api/tasks/assign/api/tasks/create/api/tasks/execute/api/tasks/extract/api/tasks/form-data/api/tasks/route

Roofing production, supplements, estimating, and storm workflows

Documents, uploads, measurements, weather, and price intelligence

These routes create the deliverables roofers actually need: docs, overlays, measurements, weather data, and price references.

Generate and send documentsRun roof measurement workflowsLoad hail, rentcast, and pricing data
21 routesRead and write, depending on the route
/api/document-uploads/api/document-uploads/create/api/document-uploads/delete/api/documents/api/documents/generate/api/documents/generate-damage-report/api/documents/process/api/documents/send/api/generate-roof-overlay/api/price-library/api/repair-supplement/api/roof-measurements/[measurementJobId]/report/api/roof-measurements/[measurementJobId]/status/api/roof-measurements/[measurementJobId]/v3/api/roof-measurements/[measurementJobId]/v3/file/api/roof-measurements/[measurementJobId]/v3/review/api/roof-measurements/generate/api/satellite-tile/api/weather/hail-report/api/weather/hail-targeting/api/weather/rentcast-key

Operator teams and communication-heavy automations

Contacts, groups, notifications, leads, outbound, and file access

This group covers who the team is working with, what they are being notified about, and how communications and lead signals arrive.

Manage contacts and groupsRead notifications and activityHandle outbound Twilio validation, lead intake, and shared drive access
18 routesWorkspace or group-scoped read/write access
/api/cdrive/[...path]/api/contacts/api/contacts/[contactId]/api/contacts/[contactId]/activity/api/contacts/[contactId]/insurance-cert/api/groups/api/groups/[groupId]/member-contacts/api/groups/[groupId]/members/api/integrations/leads/api/mobile-openclaw-handoff/api/notifications/api/notifications/[notificationId]/api/notifications/mark-all-read/api/social-accounts/upsert/api/social/oauth/callback/api/social/oauth/start/api/twilio/outbound-test/api/twilio/validate

Robot buyers, publishers, and marketplace operations

Marketplace catalog, checkout, install, and entitlement lifecycle

These routes power the catalog, the checkout flow, install connect actions, uninstalls, and entitlement checks behind Robot Marketplace.

Browse robot listingsRun checkout and installConnect or revoke robots safely
11 routesPublic browsing plus authenticated install and commerce flows
/api/marketplace/checkout/api/marketplace/clawhub/search/api/marketplace/entitlements/api/marketplace/import/clawhub/api/marketplace/install/connect/api/marketplace/install/events/api/marketplace/install/uninstall/api/marketplace/products/api/marketplace/products/[slug]/api/marketplace/products/[slug]/verify/api/marketplace/webhook/stripe

Workspace owners, admins, and external integrators

Billing, invitations, API keys, and demo content

These routes handle money, access, and integration setup: invitations, API keys, billing sessions, and demo assets used in product storytelling.

Create API keysManage billing stateInvite new teammates into a workspace
11 routesAuthenticated workspace admin or scoped API access
/api/billing/checkout/api/billing/portal/api/billing/snapshot/api/billing/webhook/api/invitations/accept/api/invitations/create/api/keys/api/keys/[keyId]/api/keys/usage/api/marketing/demo-document/api/marketing/justin-smith-demo

External OpenClaw runtimes and robot builders

BYO OpenClaw external-safe Codex and skill wrappers

This is the public builder lane for BYO OpenClaw. These routes are meant to be called over HTTPS by external runtimes without handing out raw workspace OAuth credentials.

Proxy model traffic safelyDiscover valid model idsRead Contractorfy workspace data from an external runtime
8 routesCookie, bearer JWT, or Contractorfy API key with the right scopes
/api/skills/contractorfy/codex/models/api/skills/contractorfy/codex/responses/api/skills/contractorfy/codex/status/api/skills/contractorfy/home/api/skills/contractorfy/home/job-build-calendar/api/skills/contractorfy/home/overview/api/skills/contractorfy/home/queues/api/skills/contractorfy/task-extract

Hosted Contractorfy OpenClaw flows and internal runtime control

Shared OpenClaw runtime, OAuth, pairing, and model-control surface

This is the larger control surface behind hosted OpenClaw inside Contractorfy: OAuth flows, pairing, runtime bootstrap, provider key hydration, embeddings, responses, and tenant sync.

Bootstrap and pair OpenClawHydrate provider keys and OAuth stateControl hosted Codex model traffic and runtime state
36 routesFirst-party session or tenant-scoped runtime auth
/api/openclaw/agent-builder/api/openclaw/auth-check/api/openclaw/bootstrap/api/openclaw/mobile-handoff/api/openclaw/node-bootstrap/api/openclaw/pairing-notification/api/openclaw/runtime-scope/api/openclaw/ws-auth/api/openclaw-codex/apikey/api/openclaw-codex/connect/api/openclaw-codex/embeddings/api/openclaw-codex/gemini/clear/api/openclaw-codex/gemini/oauth/callback/api/openclaw-codex/gemini/oauth/start/api/openclaw-codex/gemini/status/api/openclaw-codex/internal/connect/api/openclaw-codex/internal/sync/api/openclaw-codex/model/api/openclaw-codex/models/api/openclaw-codex/oauth/bind-tenant/api/openclaw-codex/oauth/callback/api/openclaw-codex/oauth/cancel/api/openclaw-codex/oauth/clear/api/openclaw-codex/oauth/logout/api/openclaw-codex/oauth/mobile-complete/[loginId]/api/openclaw-codex/oauth/poll/api/openclaw-codex/oauth/start/api/openclaw-codex/oauth/web-import/api/openclaw-codex/oauth/web-poll/api/openclaw-codex/oauth/web-start/api/openclaw-codex/provider-keys/api/openclaw-codex/provider-keys/hydrate/api/openclaw-codex/responses/api/openclaw-codex/responses/[responseId]/api/openclaw-codex/responses/[responseId]/cancel/api/openclaw-codex/status

Build + sell

The strategic point is not just to automate your own shop

The bigger move is to turn the workflows you already trust into a public catalog that other roofing companies can buy from. That is the difference between internal tooling and a real marketplace business.