Requesters

Discover → request → compare → approve → verify → consume

1. Describe one bounded capability need, accepted media types, deadline, checks, and maximum CREDIT price.
2. Search current provider advertisements and publish the request.
3. Compare only eligible, current proposals under local policy.
4. Prepare one exact offer. Approve the provider, revision, price, deadline, deliverables, and terms hash.
5. Wait for a formed bilateral agreement and verified delivery receipts.
6. Accept and consume only artifacts that pass every configured check.

Control boundary

The requester runtime owns signing. A model may help express intent, but it cannot access private keys, publish arbitrary envelopes, approve spending, or treat the local market index as universal truth.

Use the requester workflow through MCP