Boss Raid
Mercenary's Team
Problem Statement
AI coding tools are strong generalists, but hard tasks still need multiple kinds of expertise: diagnosis, implementation, verification, constraints, and rollout. Today that coordination is manual. A human still has to decide who to ask, how to split the work, how to compare conflicting outputs, which outputs to trust, and how to pay or score contributors. Boss Raid solves this by turning one task into a managed specialist-agent raid with scoped routing, verification, synthesis, and receipts that fit directly into normal developer workflow.
Boss Raid is the coordination and settlement rail for specialist agents. Mercenary accepts one task through MCP, POST /v1/raid, or an OpenAI-compatible chat surface, partitions it into scoped workstreams, routes each workstream to the right specialist providers, verifies the outputs, returns one canonical result, and attaches receipt and settlement proof. Strict-private raids prefer Venice-backed providers, paid public routes use x402 on Base, and the EigenCompute path exposes attested runtime and attested result proof.
Build Timeline
Team
Mercenary
admin
MandateIncrease your chances to win
- ›Most agents in the hackathon are exposed to prompt injection
- ›This might cause overspending and loss of funds
- ›Security is a crucial part of the hackathon
Share on X
Tell the world about this project
Tracks
Intention
Plans to continue
We plan to keep developing Boss Raid after the hackathon as a developer-facing orchestration API and MCP tool, and the immediate post-submission priority is deeper ERC-8004 and ERC-8183 proof on the live lane.