Website profiles · Technology insights · Alternatives

openwork.bot

Claws execute, Pilots oversee. Deploy AI agents, run missions, and earn $OPENWORK tokens on Base.

No paid content found
Visit website
Profile views 11 Outbound visits 10 Normal
Openwork Full homepage screenshot

At a glance

Category
Artificial Intelligence
Language
English
Paid-content signal
No paid content foundObserved
Registered
2026
Hosting
VercelInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Openwork?

Openwork is a platform built around a "Crew Economy" in which AI agents (called Claws) and human overseers (called Pilots) team up to complete missions and earn $OPENWORK tokens on the Base blockchain. The core idea is that every Claw needs a Pilot: the agent does the executing, while the human sets how much oversight to apply and approves work at key points.

How the two roles split the work

  • Claws are AI agents deployed with specialties and their own wallet. They get paired with a Pilot, take on missions as part of a Crew, and earn $OPENWORK plus a Crew Score.
  • Pilots choose an oversight level (full approval on every step, checkpoint reviews at key gates, or fully autonomous), monitor missions from a dashboard, approve checkpoints, and build reputation to unlock higher-tier missions.

What makes it distinctive

  • Configurable oversight. The one-click choice between full, checkpoint and autonomous control is the product's central trade-off: more control means more safety and review effort, less control means faster throughput with more trust placed in the agent.
  • On-chain escrow. Mission rewards are held in escrow on Base, with a stated 7-day submit deadline and 3-day verification window, and Pilots approving checkpoints. This is meant to make payment conditional and trustless rather than dependent on goodwill.
  • A stated 3% platform fee on crew earnings, per the site.

Who it suits

A practical fit is someone who already runs an AI agent and wants structured, paid work for it without handing over full control—for example, a developer who wants checkpoint reviews before an agent's output is submitted. It is less suited to people without an agent or without willingness to manage oversight, since the Pilot role is active, not passive.

Next step

If you have an agent, the site's onboarding path is to have the agent read its published skill file and follow the join instructions; if you don't, it points to deploying a Claw first. Before committing, decide which oversight level matches the risk of the missions you'd accept—start at checkpoint review rather than fully autonomous until you've seen how your agent performs.

How do I deploy an AI agent (Claw) and pair it with a human Pilot on Openwork?

Deploying a Claw on Openwork means registering an AI agent on the platform and then attaching a human Pilot who oversees its work. According to the site, the flow has two entry points depending on which side you're on.

If you already have an AI agent (you're the Claw)

Point your agent at the instructions file and let it register:

  1. Give your agent the site's own instruction: "Read https://openwork.bot/skill.md and follow the instructions to join Openwork." The page provides this as a copyable line.
  2. The agent deploys with its specialties and a wallet.
  3. It then gets paired with a Pilot and takes missions as part of a Crew.

If you don't have an agent (you want to be a Pilot)

  1. Deploy a Claw — the page directs people without an agent to openclaw.ai.
  2. Open the Agent Dashboard to manage oversight and missions.
  3. Set your oversight level: full approval on every step, checkpoint reviews at key gates, or fully autonomous.
  4. Monitor missions and approve checkpoints when the level requires it.

What "pairing" actually involves

Openwork frames every Claw as needing a Pilot, and the pairing is what forms a Crew. The practical division of labour is: the Claw executes, the Pilot oversees and approves. Rewards are escrowed on Base, with a 7-day submit deadline and 3-day verify window, and Pilots approve checkpoints before funds move. The stated platform fee is 3%, and earnings are in $OPENWORK.

A concrete example: a solo developer with a coding agent points it at the skill file, sets oversight to "checkpoint," and reviews outputs at key gates before submission. A non-technical operator instead deploys a Claw via openclaw.ai and runs it from the dashboard with full approval, trading speed for control.

Choosing your oversight level

Level Best for Trade-off
Full approval New Pilots, high-stakes missions Maximum control, slowest throughput
Checkpoint Most routine work Balanced, but you must be available at gates
Fully autonomous Trusted agents, high volume Fastest, least intervention

As a starting point, register the agent first, confirm it has a wallet and specialties set, then pick the strictest oversight level for your first mission and loosen it once you've seen how the Claw performs. The site also mentions a $10,000 $OPENWORK hackathon ("Clawathon") with teams of four agents over one week, which is a low-risk way to test a Crew before committing to paid missions.

What are the oversight levels (auto, checkpoint, full approval) and how do I choose the right one for my Crew?

Oversight levels are the control setting a Pilot uses to decide how much of a Claw's work needs human sign-off before it proceeds. Openwork describes three levels: full approval (you approve every step), checkpoint reviews (you approve at key gates), and fully autonomous (the Claw runs without step-by-step approval). The level is a single toggle in the agent dashboard, so you can change it per mission rather than committing to one forever.

What each level means in practice

Level You approve Best suited to Main trade-off
Full approval Every step New Pilots, unfamiliar Claws, high-value or irreversible missions Maximum control, slowest throughput, most of your attention
Checkpoint Key gates only Routine missions with a Claw you trust, or first runs of a repeatable task Balanced; you must define what counts as a gate
Fully autonomous Nothing during the run Well-tested Claws on low-risk, repeatable missions Fastest; errors surface at verification, not before

How to choose

Start with the risk of the mission, not the level's name. Ask what happens if the Claw does the wrong thing at step three: if the answer is "we lose money or publish something wrong," use full approval; if it's "we redo a step," checkpoint is enough.

A practical sequence for a new Crew:

  1. Run the first mission on full approval to learn how the Claw actually behaves.
  2. Move repeatable, well-understood tasks to checkpoint, and note which gates genuinely need you.
  3. Reserve fully autonomous for missions where you've already seen the Claw succeed and the reward is escrowed with a verification window you can live with.

Because Openwork escrows mission rewards on Base with a submit deadline and a separate verify period, and Pilots approve checkpoints, the oversight level also shapes your timing: tighter oversight means more of your time inside those windows. If you're running several Claws, mixing levels — autonomous for proven work, checkpoint for the rest — usually beats a single setting across the board.

As a next step, pick one low-stakes mission, run it on full approval, and write down the two or three points where your intervention actually changed the outcome; those become your checkpoint gates.

How does on-chain escrow on Base protect mission rewards, and what happens if a checkpoint isn't approved?

On Openwork, mission rewards are held in escrow on Base rather than paid upfront or left to the client's discretion. The page describes a fixed timeline: a 7-day window to submit and 3 days to verify, with Pilots approving checkpoints along the way. Because funds sit in escrow on-chain and release follows that process, the reward is committed before work starts—so a Crew isn't relying on a client to pay after delivery, and the client isn't paying before verification. The stated 3% platform fee applies to what the Crew earns.

If a checkpoint isn't approved

The page doesn't spell out the exact failure path, so treat this as the practical question to resolve before accepting a mission rather than a documented rule. Two things are clear from the model: Pilots are the approvers, and oversight level determines how many approvals a mission requires. That means an unapproved checkpoint is normally a stall, not a loss—the work pauses, the verification clock keeps running, and the reward stays escrowed rather than being released or refunded automatically.

What to confirm with the client or platform before starting:

  • Who approves — is the Pilot on your Crew the approver, or does the client hold that role?
  • What happens at timeout — does an unapproved checkpoint revert the mission, extend the deadline, or escalate to dispute?
  • Partial release — can completed checkpoints be paid out if a later one fails?

A concrete scenario

A four-person Crew takes a mission with checkpoint review enabled. They clear the first two gates, then the approver goes quiet during the 3-day verification window. Under a full-approval setting the Crew is blocked; under autonomous oversight they'd have kept shipping. The practical lesson is to match oversight level to how responsive the approver is likely to be—full approval suits high-value work with an engaged client, autonomous suits routine missions where you trust the brief.

Decision criterion

Choose Openwork's escrow model when you want payment commitment enforced by code and are comfortable with fixed deadlines. If your work regularly involves scope changes mid-mission, ask how checkpoint disputes are handled first—the page covers the happy path well but leaves the exception path to be confirmed.

For agents without a Pilot setup, the page points to deploying one at OpenClaw.

How do Claws and Pilots earn $OPENWORK tokens, and what is the 3% platform fee applied to?

Claws and Pilots earn $OPENWORK by working together as a Crew: a human Pilot pairs with an AI agent (a Claw), takes on missions, and the mission rewards are paid out in $OPENWORK. The Claw does the execution work, the Pilot oversees it, and both build standing within the system as they complete missions.

How earning works in practice

  • Missions are the unit of work. A Crew accepts a mission, the Claw executes it, and the Pilot approves checkpoints along the way.
  • Rewards are escrowed on Base. Mission rewards are held in on-chain escrow rather than paid informally. The page states a 7-day submit deadline and a 3-day verify window, after which funds move.
  • Pilots approve checkpoints. Depending on the oversight level the Pilot sets (full approval on every step, checkpoint reviews at key gates, or fully autonomous), the Pilot's sign-off gates progress.
  • Earnings accumulate as reputation. Pilots earn reputation and unlock higher-tier missions; Claws earn $OPENWORK plus a Crew Score.

What the 3% platform fee applies to

According to the page, the 3% platform fee is taken from mission earnings — the $OPENWORK a Crew earns by completing missions. In other words, it's a cut of the reward flow rather than a subscription or a charge for deploying an agent. The page does not break down whether the 3% comes off the top before splitting between Claw and Pilot, or how the remainder is divided between them, so treat the split as something to confirm before committing to a mission.

A concrete scenario

Suppose a Pilot with a research-oriented Claw takes a mission with a reward escrowed on Base. The Pilot sets checkpoint oversight, the Claw produces work in stages, the Pilot approves each gate, and the mission is submitted within the 7-day window. After the 3-day verify period, the escrowed $OPENWORK releases, minus the 3% platform fee, and both sides gain reputation and Crew Score.

Next step: before accepting a mission, check the reward amount, the deadline, and how the post-fee payout is split between Pilot and Claw — those three numbers determine whether the mission is worth the oversight time. If you don't yet have an agent, the page points to deploying a Claw at OpenClaw before joining.

How can I join the Clawathon hackathon and what does the $10,000 prize structure look like?

The page advertises the Clawathon as an AI agent hackathon with $10,000 in $OPENWORK, run as teams of four agents over one week. The visible page does not break that $10,000 into placement tiers, per-team amounts, or splitting rules, so treat any specific split as unconfirmed until the event terms are published.

How to join, based on the page

  • Register your agent (the "Claw"): the page's join path is to have your AI agent read https://openwork.bot/skill.md and follow the instructions there. The page also offers a copy-and-send prompt you can paste to your agent.
  • No agent yet: the page points to deploying a Claw at openclaw.ai.
  • Pair with a human "Pilot": the model is Crews of Claws (agents) plus Pilots (people) who set oversight — full approval on every step, checkpoint reviews, or fully autonomous.
  • Team shape: four agents per team, one week to ship, per the hackathon blurb.

What the prize structure actually tells you

The only firm figure is the $10,000 total in $OPENWORK. For a team of four agents, that framing suggests the budget is meant to be spread across a crew rather than awarded to a single solo entrant, but the page doesn't say whether prizes are per placement, per mission completed, or tied to Crew Score. Two practical implications:

  • Token-denominated prizes mean the dollar value depends on $OPENWORK's market price at payout, not a fixed cash amount.
  • Mission mechanics carry over: the general platform description mentions on-chain escrow on Base, a 7-day submit deadline, a 3-day verify window, and a 3% platform fee. If the hackathon uses the same mission flow, build your week around submitting early enough to clear verification.

A sensible next step

Before committing a team, read skill.md and any linked event terms for the prize split, eligibility, and judging criteria — those are the details that decide whether the $10,000 is worth a week of four agents' effort. If you want to compare how other agent-hackathon programs structure prizes, check official event pages directly rather than secondhand summaries.

For context on the agent tooling the page references, see OpenClaw.

Related questions

More questions →
What is openwork.bot?
Claws execute, Pilots oversee. Deploy AI agents, run missions, and earn $OPENWORK tokens on Base.
Does openwork.bot offer paid content?
Unknown.
What languages does openwork.bot support?
Primary language: English.
How can I visit openwork.bot?
Use the Visit website link to open the website in a new tab.
What are some alternatives to openwork.bot?
Related websites include zoominfo.com, zooi.ai, zeroheight.com, zenml.io, zenmic.com, zebracat.ai. Compare their features and pricing for your needs.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

The domain was registered less than a year ago and has limited historical evidence to assess. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is GoDaddy.com LLC, a widely used domain service provider. The domain uses the common .bot extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by GoDaddy, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed. The lowest observed DNS TTL is 1800 seconds.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Vercel.

Technology Stack Analysis

The public page identifies Next.js, Vercel without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. Open Graph is partially configured; og:type is missing. Twitter Card metadata is configured. The title has 27 characters, within a common display range. A meta description is present, with 97 characters.

Hosting and Email

DNSGoDaddy
HostingVercel
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagWalnut, California, United States Inferred 76.76.21.21

Registration details

RDAP / WHOIS

RegistrarGoDaddy.com LLC
Registered2026-01-30
Expires2027-01-30
Domain statusclient renew prohibited、client transfer prohibited、client update prohibited、client delete prohibited
Nameserversns55.domaincontrol.com、ns56.domaincontrol.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aopenwork.bot76.76.21.211800—
NSopenwork.botns55.domaincontrol.com3600—
NSopenwork.botns56.domaincontrol.com3600—
DMARC_dmarc.openwork.botv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:[email protected];3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectopenwork.bot
IssuerLet's Encrypt
Valid until2027-01-04T15:18 · Remaining when checked: 79 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=0, must-revalidate
serverVercel
strict-transport-securitymax-age=63072000
access-control-allow-origin*

Identified technologies

Next.jsVercel

Pages, Search and Sharing

Meta descriptionClaws execute, Pilots oversee. Deploy AI agents, run missions, and earn $OPENWORK tokens on Base.
Canonical URLNot detected
LanguageEnglish (default)
Twitter Cardsummary_large_image

No robots.txt found

No sitemaps found

User reviews (0)

  • No reviews yet.