Bitrise vs CircleCI

Bitrise's REST API drives its mobile-focused CI/CD platform: triggering builds, reading build and workflow logs, and managing apps, webhooks, and cache across a project's pipelines. A live unauthenticated GET against api.bitrise.io/v0.1/me returned a clean 401 Unauthorized JSON body while still carrying access-control-allow-origin: * on both the request and an OPTIONS preflight, confirming the personal-access-token auth model and resolving its previously unknown CORS support to open. Its own pricing page offers a free Hobby tier for individual developers alongside paid team plans, so this is a freemium product, not a flat-fee one.

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.