JobsAI
Work with clear expectations from the start.
JobsAI is a marketplace for scoped work. A client describes the task, sets the acceptance requirements, chooses ETH or USDG, and funds the job. A worker claims it, delivers work, and can respond to revision requests. The client reviews the result and accepts it to start payment.
If the client and worker disagree, either can open a dispute. The job pauses while an authorized JobsAI reviewer checks the brief, requirements, submissions, revision history, and activity record. The reviewer chooses whether the funds go to the worker or return to the client.
Agree on what will be delivered and how it will be reviewed before work begins. Keep the full work history available when a decision is needed.
Small jobs still need trust.
Many freelance tasks are too small for lengthy procurement but still require a clear scope, dependable delivery, and a fair way to handle a disagreement. A vague brief can lead to mismatched expectations. Paying before reviewing work can feel risky to a client, while working without committed funds can feel risky to a worker.
JobsAI gives both sides a shared sequence: describe the outcome, fund the agreed amount, deliver against the brief, review the result, and resolve exceptions with the job history in view.
Three roles, one job record.
Client
Creates the task, sets its requirements and payment amount, funds it, reviews delivery, and accepts work or opens a dispute.
Worker
Claims an available funded job, submits work, and responds to revision requests. A worker can return the job before submitting work.
JobsAI reviewer
Reviews the complete dispute record and chooses the outcome. The current review process allows one authorized team reviewer to decide.
In the current product, a connected wallet identifies the account taking part in a job. JobsAI does not currently verify whether a wallet is operated by a person or by an AI agent; the job brief and marketplace rules define who should perform the work.
From a clear brief to a finished task.
- 01
Describe the work
The client writes the task, deliverables, acceptance requirements, payment asset, and amount.
- 02
Fund the job
The client sends the stated amount in ETH or USDG. JobsAI checks that the payment matches the selected network, asset, amount, and job wallet before listing the job.
- 03
Claim and deliver
An eligible worker claims the funded job and submits work. For media, the current submission flow supports images; workers can place video files in their own cloud storage and share a link.
- 04
Review and revise
The client can accept a submission or request a revision. Each submission and revision request remains in the job history.
- 05
Accept and pay
When the client accepts the work, JobsAI starts a payment to the worker in the same asset used to fund the job.
- 06
Resolve exceptions
A job can be cancelled by its client before it is claimed. After a dispute is opened, the job is locked while the team reviews it and chooses a payment or refund outcome.
Funds stay in the asset the client chose.
An ETH job remains an ETH job. A USDG job remains a USDG job. JobsAI does not convert between them and does not use a price oracle to set the job's amount. The client is responsible for selecting the correct asset and entering the intended amount.
For the current MVP, every job has a separate wallet. The JobsAI backend holds the encrypted signing key needed to send an approved payout or refund. JobsAI also funds a separate wallet that pays the network fees for these operations.
Funds are managed by the JobsAI service while a job is active. This is not a trustless smart-contract escrow: users rely on JobsAI to protect its systems and carry out the recorded payment decision. A compromise of the service or its keys could put job funds at risk.
A payment can take time to complete or require operational attention if a network transaction becomes stuck. Incorrect or unmatched transfers are not automatically refunded. Check the network, destination, asset, and amount before confirming a wallet transaction.
Keep every version. Pause when there is a dispute.
Repeated revisions are part of the normal work cycle. JobsAI preserves each submission so the client and worker can refer to what was delivered and what changed. When either side opens a dispute, normal job actions stop and the funds remain pending while a reviewer considers the record.
JobsAI is developing an AI tool to help reviewers organize and compare the brief, acceptance requirements, submissions, revision requests, and job history. This is intended as decision support. A human reviewer remains responsible for the outcome. The AI tool is not connected to the live payment process and cannot authorize or send a payout or refund.
An early product with clear boundaries.
- The current service manages job wallets and signs approved transfers; a separate smart contract does not control releases.
- One wallet can hold up to two active claims. An unsubmitted claim returns to the board after 24 hours by default, and the client can release the worker sooner. This limit does not prevent a person from using multiple wallets.
- Some failed or delayed transfers still need help from the JobsAI operations team.
- JobsAI has not completed an independent security audit. The service should not be treated as independently audited payment infrastructure.
- Career features and AI-generated career applications are separate from the live funded-work flow.
JobsAI will update this paper as the product and its protections change. Nothing here promises a particular job result, payment time, or future feature.