Task offer API — agents post work offers with locked XLM reward

[leocagli]

Problem

Agents can only receive tasks from humans via the orchestrator. There is no way for an agent to offload work to another agent and track the result.

API design

POST /api/task-offers
{ "requiredCapability": "run-inference", "payload": {...}, "reward": "0.05 XLM", "deadline": 1750000000 }
? { "offerId": "off_abc", "escrowTx": "..." }

GET /api/task-offers?cap=run-inference   � list open offers
GET /api/task-offers/:id                 � single offer detail
DELETE /api/task-offers/:id              � cancel (refunds escrow, poster only)

Posting an offer locks the reward in the existing Soroban escrow contract. The deadline is enforced server-side: expired unclaimed offers auto-refund.

Schema

interface TaskOffer {
  offerId: string
  postedBy: string           // agentId
  requiredCapability: string
  payload: unknown
  reward: { amount: string; asset: 'XLM' | 'USDC' }
  deadline: number
  status: 'open' | 'claimed' | 'delivered' | 'accepted' | 'disputed' | 'expired'
}

Files to create

• app/api/task-offers/route.ts
• app/api/task-offers/[id]/route.ts
• lib/task-market/offers.ts

[leocagli]

Self-contained API layer. The escrow integration reuses the existing Soroban escrow client in lib/protocols/escrow.ts — no contract work needed here, just the REST endpoints and DB schema.

[wuleilonghundao-svg]

Hi! I inspected this against the current task-offer follow-ups and saw the maintainer note that #113 should be a self-contained API layer reusing lib/protocols/escrow.ts, with no contract work needed.

I also noticed #156 covers the smaller GET/POST /api/task-offers board-wiring task and is already approved/assigned to @ekwe7, so I do not want to duplicate that narrower scope.

Would you still want a separate PR for #113 focused on the broader API surface and schema, e.g.:

• lib/task-market/offers.ts with the full TaskOffer model, expiry handling, and storage boundary
• GET/POST /api/task-offers
• GET/DELETE /api/task-offers/[id]
• integration through the existing escrow client in lib/protocols/escrow.ts
• focused endpoint tests for create/list/detail/delete/expiry behavior

If #156 is intended to cover the whole backend API surface, I will leave this alone. If #113 is still open as the broader task-offer API work, I can take that route and keep the PR scoped to this issue.