GitHub vs Teamwork.com for AI agents
As of 13 Oct 2026, GitHub gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: No key needed, sign-up in a browser.
- Use: 89% of the work.
- Pay: Payment not tried: robots.txt keeps our agent off the payment page for now.
- Leave: Leaves on its own: Nothing to cancel, made nothing to delete.
Through every checkpoint. Next: pay without a person
Runs on its own once it holds an existing identity: L4 · Runs on its own. Sign-up itself never got past a block on the signup page, so every later call ran on an existing account approved once through device-flow login. From there the work ran headless: REST, GraphQL, the gh CLI and the official MCP server created repos, commits, pull requests, reviews, issues and Actions runs, repeated across the core work. Codespaces refused our datacenter network, and the cloud coding agent needs a paid plan, so neither ran. Nothing to cancel on the free plan; account deletion is documented as web-only, so our agent revoked its grant and left the identity in place.
Gets furtherDriven 13 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Needs a person. Sign-up stops at the account form: after passing an invisible reCAPTCHA, it asks for a phone number our agent did not have, and no human supplied one. The account was never created. With no account, the key page, the official MCP server and the Swagger-documented endpoints stayed out of reach. Our agent got only an unauthenticated 401 from the API and from MCP's tools list, and no work was attempted. The pricing page lists a trial without a card and payment by card or bank transfer, but checkout sits behind the same sign-up form: our agent never reached it, and never had an account to cancel or delete.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
GitHubThrough every checkpoint
Teamwork.comStopped at sign up: blocked
| Checkpoint | GitHub | Teamwork.com |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Blocked |
| Verify | Not needed | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Not tried | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Blocked | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| GitHub | Teamwork.com | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 1 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 1 | 1 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 89% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | No |
| SDK | – | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| GitHub | Teamwork.com | |
|---|---|---|
| Bot check | A challenge on the form stopped one way in (Email and password); it got in another way | reCAPTCHA (invisible) let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | None | Phone number required at sign-up |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| GitHub | Teamwork.com | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Holds up | 59 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 90 of 100, good |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · OpenAPI 3.0.3 (2 versions behind) | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) · OpenAPI 2.0 (3 versions behind) |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| GitHub | Teamwork.com | |
|---|---|---|
| Pay | Payment not tried | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not needed | Not reached |
| Delete the account | Blocked | Not reached |
How each one takes payment
- GitHub: Not tried yet: robots.txt keeps our agent off the payment page for now.
- Teamwork.com: Payment not reached.
GitHub vs Teamwork.com: the short answers.
Which can an AI agent use, GitHub or Teamwork.com?
GitHub gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With GitHub our agent went through every checkpoint; with Teamwork.com it was stopped at sign up (blocked). Driven 13 Oct 2026 (GitHub) and 6 Oct 2026 (Teamwork.com).
Can an AI agent sign up for GitHub and Teamwork.com on its own?
GitHub: not needed. Teamwork.com: no, blocked.
Do GitHub and Teamwork.com have an MCP server?
GitHub: yes (official). Teamwork.com: yes (official).
Can an AI agent delete its GitHub or Teamwork.com account?
GitHub: blocked. Teamwork.com: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.