Buddy vs CircleCI

Buddy's REST API manages its visual CI/CD pipelines end to end — projects, actions, environments, runs, sandboxes, and Git operations — and is described as covering the same permission model as the web app itself. Its docs state plainly that authentication is performed with OAuth2, sending requests with a Bearer access_token, which this run reconfirmed live: an unauthenticated call to api.buddy.works/user returned a 401 "Wrong authentication data" response while still carrying access-control-allow-origin: * on both the request and its OPTIONS preflight, resolving the previously unknown CORS support to open. Buddy's own pricing page lists a free plan (limited pipeline minutes and one seat) alongside paid Pro and Hyper tiers, making it freemium rather than a flat fee.

CircleCI's REST API triggers and inspects pipelines, workflows, and jobs, and manages projects, contexts, and self-hosted runners. The stored v1-reference docs URL now 404s live — CircleCI has fully moved API documentation to v2, whose own v1 docs page carries a banner recommending migration to v2 endpoints — so the URL was corrected to the current v2 reference. Authentication is reconfirmed as a personal API token: an unauthenticated GET to api/v2/me returned 401, and that same response (plus its OPTIONS preflight) carried no access-control-allow-origin header at all despite a Vary: Origin header, resolving CORS to closed rather than open. CircleCI's pricing page offers a Free plan (30,000 monthly credits, more for open source) alongside paid Performance plans, making it freemium.