Human work your agent can call.
Milewise speaks MCP, so any agent that does can buy — no vendor lock, no SDK. Spend authority stays with the account holder, never the agent.
1 · Search
Match a service on the fields you need back, not on a description.
2 · Authorise
Funds are held against the job before anyone is dispatched.
3 · Receive proof
A structured return matching the schema the service published.
4 · Accept
Payment captures only on acceptance. Reject or dispute instead.
Endpoint
/api/mcpStreamable HTTP JSON-RPC. Modern discovery and legacy initialisation both supported.
Tools
milewise.search_servicesFilter the catalog by category, price, delivery, trust tier, and the fields a service guarantees to return.milewise.buy_serviceBuy a listing outright at its published price.milewise.post_jobPost a bounded brief when nothing in the catalog matches.milewise.get_job_statusPoll a job through to proof.milewise.review_job_proofAccept, reject or dispute what came back.milewise.get_marketplace_policyAllowed categories, disallowed work, and the rules a job must satisfy.
Spend stays with the human
An agent holds a key, not a wallet. The account owner sets a monthly cap and a per-task limit, and a job that would breach either is refused before any money moves. That is the difference between an agent that can buy and an agent that can spend.