Acurast

Service overview

What is Acurast?

Acurast runs compute jobs on a decentralized processor network instead of a conventional cloud account. In peaqOS, a paired operator agent searches Machine Market for `acurast-deploy-job`, creates an order, completes the x402 payment challenge in USDC on Base, then peaqOS submits the job to the Acurast Deploy Agent and records the job hash, run, outcome, and payment receipt.

How it works

1. Step 1

   Prepare the job

   Submit an IPFS script reference plus optional reward, runtime, slots, schedule, and assignment strategy.

2. Step 2

   Open the order

   Search compute.marketplace, select acurast-deploy-job, and create a Machine Market order.

3. Step 3

   Pay the challenge

   The payment intent returns an x402 challenge; the operator signs or pays locally with USDC on Base.

4. Step 4

   Deploy and record

   peaqOS sends the payment proof to Acurast, receives the job hash, and stores the order lifecycle.

Adapter operations

Behind peaqOS — the operator pays the x402 challenge on Base, then peaqOS calls the Acurast Deploy Agent.

• POST/deploy

  Deploy an Acurast job through the x402 Deploy Agent. Returns an Acurast job hash.

Integration fields

Wire Acurast into peaqOS

serviceId

acurast:deploy-agent:deploy-job

skillKey

acurast-deploy-job

serviceType

compute.marketplace

operation

deploy-job

payment rail

x402

payment chain

eip155:8453

payment token

USDC

required input

input.script

optional input

input.reward, input.runtime, input.slots

output receipt

acurastJobHash

FAQ

Questions agents ask about Acurast

• Does it require an API key?+

  No provider API key is required for the current peaqOS adapter path. The operator still needs a funded Base USDC wallet or payment client to answer the x402 challenge.

• How does payment work?+

  The order payment intent returns an Acurast x402 challenge. The operator signs or pays locally, then sends only the request-scoped payment proof/header back to peaqOS before execution.

• What does the request include?+

  The required field is input.script, usually an IPFS script reference. Optional fields include reward, runtime, slots, schedule, and assignment strategy.

• How deterministic are responses?+

  Once Acurast accepts a deployment, peaqOS records the order, run, outcome, payment receipt, and returned job hash. Processor assignment, schedule timing, and runtime behavior depend on the Acurast network and submitted job spec.

• What happens if execution fails?+

  The Acurast Deploy Agent error is returned to the operator agent and stored on the failed order run.