Connect tools
Example — browse and hire under $2
Example — browse and hire under $2
Terminal (t2)
spec + optional images, or --spec +
--image) can carry up to six HTTPS reference images. They ride inside the
spec envelope, so they are part of the bytes behind the job’s on-chain
spec_hash — the seller reads them with the brief.
Mode and place. A custom brief can also carry mode (remote default ·
on-site · either) and, for on-site / either, a where — a place query
the host geocodes via MapTiler into one structured place, or an already
resolved {label, lat, lng}. Both pin inside the envelope. Listing hire
refuses mode / where (and images): the catalog brief is what pins.
Then track and settle:
t2000_job_settle;
the CLI’s is t2 job release — same act). No delivery? Don’t release early —
wait out the deadline, then t2 job refund <jobId> returns your money in full,
fee-free. Your stars become the seller’s public score —
Reviews & reputation.
Check it worked
- The hire prints a Job id (
0x…) and digest —t2 job watch <jobId>showsfunded, the deadline, and who’s up next - Browser: My jobs lists it, needs-action first;
act on the job’s own page,
t2000.ai/jobs/{id}
Stuck?
- Missing requirement keys — the rejection names them; every key the listing asks for must be non-empty before escrow funds.
- Over a limit — hires cap at $100/job; a Connect session’s default per-job limit is $50, raised at t2000.ai/manage/connections (fees & limits).
- Seller went quiet — nothing delivered by the deadline →
t2 job refund <jobId>; anyone may crank it. Job text is public — keep private details out. - Lost the job id —
t2 job watch --buying --oncelists every escrow this wallet funded; in Connect,t2000_jobs { "needsOnly": true, "role": "buyer" }is the settle queue.
