Buddy
Buddy · Developer tools
CI/CD pipelines: workspaces, projects, pipelines and executions
The client pastes their personal access token from Buddy's settings. We store it encrypted.
Tested against Buddy's live API.
Building with Buddy? The docs have setup steps and code for every tool.
Open the Buddy docsTools
Your agent calls any endpoint of Buddy's API with the request tool, with the client's access attached.
Base URL for request
https://api.buddy.works
request
HTTPS ANY /v1/clients/{clientId}/buddy/{path}
Any endpoint of Buddy's own API, with the client's access attached.
- servicestringrequired
- This service: buddy
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://api.buddy.works
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the Buddy key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.