Gitea
Gitea is an open-source, self-hosted Git service and all-in-one DevOps platform written in Go and licensed under the MIT License. It provides Git hosting, code review, team collaboration, an integrated package registry across 24+ formats, issue tracking, project boards, and GitHub-Actions-compatible CI/CD via Gitea Actions. Gitea ships with a comprehensive Swagger 2.0 / OpenAPI-described REST API at /api/v1/ exposing roughly 300 operations across repositories, users, organizations, issues, packages, notifications, admin, and miscellaneous tags. The project is governed by CommitGo, Inc., which also offers Gitea Enterprise (self-managed, with SSO, audit logs and Kubernetes auto-scaling runners) and Gitea Cloud (single-tenant fully-managed hosting in multiple regions).
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Gitea the way a machine reads it — 130 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Gitea scores 77.4/100 (exemplar), with a separate agent-readiness read of 74/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Gitea
Each block below is one kind of artifact we hold for Gitea. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Gitea Actions API
GitHub-Actions-compatible workflow engine embedded in Gitea. The Actions API surface is exposed under the main REST API (/repos/{owner}/{repo}/actions/* and /admin/actions/*) fo...
Gitea Package Registry
Multi-format package registry built into Gitea exposing client protocols for 24 ecosystems including Cargo, Composer, Conan, Conda, Container (OCI), CRAN, Debian, Generic, Go, H...
Gitea Webhooks
Outbound HTTP webhook system delivering JSON event payloads for pushes, pull requests, issues, releases, package events, and more. Webhooks are configurable per repository, orga...
Gitea Cloud Management API
Gitea Cloud management plane for provisioning and operating single-tenant managed Gitea instances. Each provisioned instance exposes the same REST API at /api/v1/. The managemen...
Gitea admin API
The admin API from Gitea — 22 operation(s) for admin.
Gitea issue API
The issue API from Gitea — 34 operation(s) for issue.
Gitea miscellaneous API
The miscellaneous API from Gitea — 12 operation(s) for miscellaneous.
Gitea notification API
The notification API from Gitea — 4 operation(s) for notification.
Gitea organization API
The organization API from Gitea — 37 operation(s) for organization.
Gitea package API
The package API from Gitea — 7 operation(s) for package.
Gitea repository API
The repository API from Gitea — 133 operation(s) for repository.
Gitea settings API
The settings API from Gitea — 4 operation(s) for settings.
Gitea user API
The user API from Gitea — 48 operation(s) for user.
Scroll within the panel for all 13 ·
Postman Collections 2
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Gitea API
OPEN COLLECTIONArazzo Workflows 19
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Gitea Bootstrap Repository With Tracking Issue
Create a repository, open a tracking issue in it, and add a kickoff comment.
ARAZZOGitea Feature Branch To Merged Pull Request
Create a feature branch, open a pull request, and merge it.
ARAZZOGitea Commit File On New Branch And Open Pull Request
Create a branch, commit a new file to it, and open a pull request.
ARAZZOGitea Create Branch And Await Availability
Create a branch and poll until it is retrievable from the repository.
ARAZZOGitea Draft Then Publish Release
Create a draft release, attach an asset, then publish the release.
ARAZZOGitea Create Label And Apply To Issue
Create a repository label and apply it to an existing issue.
ARAZZOGitea Create Milestone With Tracked Issue
Create a milestone and open an issue assigned to that milestone.
ARAZZOGitea Sync Mirror And Confirm Branch
Confirm a repository is a mirror, trigger a sync, and verify a branch.
ARAZZOGitea Open And Triage Pull Request
Open a pull request and then triage it with assignees and labels.
ARAZZOGitea Bootstrap Organization With Shared Label
Create an organization, add a repository, and create an org-wide label.
ARAZZOGitea Provision Organization Repository With Webhook
Create an organization, add a repository to it, and register a webhook.
ARAZZOGitea Create Organization With Webhook
Create an organization and register an organization-level webhook.
ARAZZOGitea Create Release And Verify By Tag
Create a release and confirm it by looking it up by its tag.
ARAZZOGitea Create Repository With A Labeled Issue
Create a repository, create a label in it, and open a pre-labeled issue.
ARAZZOGitea Create Repository With Webhook
Create a repository for the authenticated user and register a webhook.
ARAZZOGitea Report Issue To Existing Repository
Confirm a repository exists, open an issue in it, and comment on it.
ARAZZOGitea Sprint Issue Setup
Create a milestone and label, open an issue under them, and apply the label.
ARAZZOScroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
gitea-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Gitea Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gitea Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gitea Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Git Repository Hosting
Self-hosted Git remote with HTTPS and SSH transport, granular repository visibility (public, private, internal), and full repository CRUD over the REST API.
Pull Requests And Code Review
Branch-based pull requests with reviewers, required approvals, status checks, draft state, conflict detection, and inline review comments.
Issue Tracking And Projects
Built-in issue tracker with labels, milestones, assignees, dependencies, and Kanban-style project boards at repo and org scope.
Gitea Actions CI/CD
Native, GitHub-Actions-compatible workflow engine driven by the act_runner agent. Supports matrix builds, secrets, and autoscaling runners on Kubernetes (Enterprise).
Package Registry
Multi-format package registry covering 24 ecosystems including Container (OCI), Maven, npm, NuGet, PyPI, Helm, Cargo, Terraform, and Generic uploads.
Webhooks And Events
Outgoing webhooks for repository, issue, pull request, release, and package events with optional secret signing.
Comprehensive REST API
Approximately 300 endpoints under /api/v1/ described by a Swagger 2.0 specification with multiple authentication schemes.
Authentication And SSO
Supports BasicAuth, personal access tokens, OAuth2 with PKCE, OpenID Connect, LDAP, SMTP, PAM, SAML SSO (Enterprise), and two-factor authentication.
Multi-Database Storage
Pluggable storage backend supporting SQLite, MySQL, PostgreSQL, TiDB, and MS SQL.
Mirroring And Migration
Pull and push mirrors plus one-shot migration import from GitHub, GitLab, Bitbucket, Gitea, and other sources.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gitea Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Gitea API Rules
SPECTRALGitea API Rules
SPECTRALJSON Schema 16
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Branch
JSON SCHEMAComment
JSON SCHEMAHook
JSON SCHEMAIssue
JSON SCHEMALabel
JSON SCHEMAMilestone
JSON SCHEMANotificationThread
JSON SCHEMAOrganization
JSON SCHEMAPackage
JSON SCHEMAPullRequest
JSON SCHEMARelease
JSON SCHEMARepository
JSON SCHEMATag
JSON SCHEMATeam
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 16 ·
JSON Structure 16
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Gitea Rest Api Branch Structure
JSON STRUCTUREGitea Rest Api Comment Structure
JSON STRUCTUREGitea Rest Api Commit Structure
JSON STRUCTUREGitea Rest Api Hook Structure
JSON STRUCTUREGitea Rest Api Issue Structure
JSON STRUCTUREGitea Rest Api Label Structure
JSON STRUCTUREGitea Rest Api Milestone Structure
JSON STRUCTUREGitea Rest Api Notificationthread Structure
JSON STRUCTUREGitea Rest Api Organization Structure
JSON STRUCTUREGitea Rest Api Package Structure
JSON STRUCTUREGitea Rest Api Pullrequest Structure
JSON STRUCTUREGitea Rest Api Release Structure
JSON STRUCTUREGitea Rest Api Repository Structure
JSON STRUCTUREGitea Rest Api Tag Structure
JSON STRUCTUREGitea Rest Api Team Structure
JSON STRUCTUREGitea Rest Api User Structure
JSON STRUCTUREScroll within the panel for all 16 ·
Examples 23
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Gitea Rest Api Hook Example
EXAMPLEGitea Rest Api Issue Example
EXAMPLEScroll within the panel for all 23 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Self-Hosted Source Control
Run a private Git server inside a corporate or air-gapped network, retaining full data ownership.
Internal Developer Platform
Combine Git, Actions, packages, and projects to build an internal developer platform without stitching together multiple SaaS vendors.
GitHub Actions Compatible CI/CD
Reuse existing GitHub Actions workflows on a self-hosted or cloud runner without depending on github.com.
Multi-Format Artifact Registry
Use Gitea as a single artifact registry for OCI containers, language packages, and generic binaries.
Regulated And Sovereign Hosting
Single-tenant Gitea Cloud regions provide data-residency options for regulated industries and EU customers.
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Gitea Actions / GitHub Actions Marketplace
GitHub-compatible workflow ecosystem; most public Actions run unmodified on Gitea Actions runners.
Drone CI
First-class integration with Drone for repository-driven continuous delivery pipelines.
Jenkins
Webhooks and credentials make Gitea a drop-in source for Jenkins multibranch pipelines.
Terraform
Official Terraform provider (terraform-provider-gitea) and a Terraform module package registry endpoint.
Kubernetes
Helm charts and operator-friendly deployment, plus Gitea Enterprise Kubernetes auto-scaling runners.
Argo CD / Flux
GitOps controllers can use a Gitea repository as the source of truth for cluster state.
Discord And Slack
Outbound webhook templates for Discord, Slack, and Microsoft Teams notifications.
Tea CLI
Official command-line client for browsing and managing repositories, issues, pull requests, and releases.
Scroll within the panel for all 8 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Gitea (Open Source)
Free, MIT-licensed self-hosted edition with the complete feature set and unlimited users.
Gitea Enterprise
Commercial self-hosted edition adding SAML SSO, audit logs, Kubernetes auto-scaling runners, priority SLA support, and installation/upgrade assistance.
Gitea Cloud
Single-tenant fully-managed Gitea hosted by CommitGo with choice of regions (including a Frankfurt EU region), 24x7 availability, and SOC 2 Type 2 certification.
Gitea Actions Runner (act_runner)
Stand-alone runner agent for executing Gitea Actions workflows on customer infrastructure.
Resources
Every other property we hold for Gitea — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 27
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 27 ·
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 8
Status, limits, changes, and where to get help
Scroll within the panel for all 8 ·
Commercial 5
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/gitea · machine-readable index on apis.io