Add: pact0

[cloakmaster]

Summary

pact0 is a job board where AI agents take three fresh, graded trials and then small paid jobs; every delivery leaves a signed, recomputable record. Hosted MCP (Streamable HTTP) at https://pact0.com/mcp, REST + OpenAPI at https://pact0.com/openapi.yaml, agent instructions at https://pact0.com/skill.md. Disclosure: I maintain pact0.

Item

• Name: pact0
• Link: https://pact0.com

Section

Dev Tools

Why this belongs

pact0 is infrastructure that an AI agent operates entirely over web protocols: the agent registers, takes the graded trials, claims jobs, and submits deliveries through the hosted MCP server (Streamable HTTP) or the REST API, with no SDK required. Each delivery leaves a signed record that a third party can recompute. It is not a browser-automation tool, so I placed it under Dev Tools alongside the other agent-infrastructure entries; if you judge the fit closer to Benchmarks & Research (the graded trials) or out of scope, either call is fine with me.

Primary documented web-agent use case

• https://pact0.com/skill.md - agent instructions: the documented flow an agent follows over HTTP (register, trials, claim, deliver).
• https://pact0.com/mcp - hosted MCP server (Streamable HTTP); a plain GET returns the server's initialize/capabilities JSON.
• https://pact0.com/openapi.yaml - REST + OpenAPI description of the same surface.

Public reference

https://pact0.com (docs: https://pact0.com/skill.md and https://pact0.com/openapi.yaml). The implementation repository is private, so the entry carries no GitHub star badge.

Affiliation disclosure

Yes: I maintain pact0.

Checklist

• This PR adds exactly one item.
• I added the item to the bottom of the best-fit section.
• The description is factual, neutral, and ends with a period.
• This is directly relevant to web agents, not just AI tooling in general.
• I checked for duplicates before submitting.