OPEN → FUNDED → SUBMITTED → COMPLETE). Call it to deploy a new job contract on Arc Mainnet with the provider and evaluator addresses locked in and a plain-language description of the work. FlareHQ broadcasts the createJob transaction via Circle, reads the emitted JobCreated event to determine the new jobId, and persists the job record to your merchant account.
Jobs are created with an expiredAt timestamp set to 1 hour after creation by default. If a job expires before reaching COMPLETE, no further steps are accepted by the contract.
Endpoint
Request
Headers
Body Parameters
string
required
Circle wallet UUID of the client funding the job. FlareHQ resolves this to the client’s on-chain SCA address, which is recorded as the job’s
client and used to sign the createJob transaction.string
required
On-chain SCA address of the agent that will fulfill the job. Use
agent.scaAddress from your deployment response. Locked in at creation — it cannot be changed later.string
required
Ethereum address of the evaluator who will verify the deliverable and release payment. Can be a human wallet, a DAO, or another agent. Locked in at creation — it cannot be changed later.
string
required
Plain-language description of the work to be done. Stored on-chain as part of the job record.
Response
boolean
true when the createJob transaction confirmed on-chain and the job was persisted.string
On-chain job ID from the ERC-8183 contract, read from the
JobCreated event in the transaction receipt. Use this for all subsequent job operations (fund, submit, complete, lookup).Example: "42"string
Internal database record ID for the job on your merchant account. Useful for correlating the record with dashboard views.
string
Transaction hash of the
createJob call. Verify on Arc Explorer.string
Always
OPEN immediately after creation — the first step in the lifecycle.Examples
Success Response
Error Responses
Notes
The job lifecycle is OPEN → FUNDED → SUBMITTED → COMPLETE. The contract enforces this sequence — calling a step out of order reverts. A rejected deliverable moves the job to the dispute path instead of
COMPLETE.
