# graphiti-api/graphiti

Stylish Graph APIs, built on JSON:API

Repository: https://github.com/graphiti-api/graphiti
Canonical: https://ross.abutalabs.com/products/graphiti-api-graphiti
Homepage: https://graphiti.dev/
Language: Ruby
License: MIT
License Family: permissive
Topics: json-api, rails, api, graphiti, microservices, ruby, ruby-on-rails
Last push: 2026-09-02T23:38:43+00:00

## Health v2 (maintenance only)
Score: 100/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 100, longevity 100
- inputs: {"age_days": 3632, "days_push": 0, "days_rel": 0, "gap_med": 2, "n_releases_24m": 26}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1059, forks 157 (observed 2026-09-03T02:15:12.517999+00:00)

## What it is
Graphiti is a Ruby framework for building JSON:API-compliant APIs on top of your models (typically ActiveRecord). It replaces hand-written controllers and serializers with declarative Resource classes that provide filtering, sorting, pagination, sparse fieldsets, statistics, and sideloaded relationships.

## Use cases
- build a JSON:API-compliant REST API in Rails
- expose ActiveRecord models with filtering, sorting, and pagination
- sideload related records in a single API request
- replace JBuilder or ActiveModelSerializers with a standardized API layer
- build consistent microservice APIs with minimal boilerplate
- support sparse fieldsets and statistics endpoints
- handle nested writes across relationships over one endpoint

## When to choose
- you are building a Rails (or Ruby) API and want JSON:API compliance out of the box
- you want filtering, sorting, pagination, and sideloading without writing boilerplate per endpoint
- your JavaScript SPA client can speak the JSON:API protocol
- you want resource-oriented API organization instead of per-controller serialization logic

## When to avoid
- you need a fully custom, non-standard JSON response shape for every endpoint
- you are not using Ruby or Rails
- your API is trivial and a simple serializer like JBuilder suffices
- you need GraphQL rather than JSON:API

## Facets
- artifact type: framework
- maturity: active
- function: serialization, api-framework, web-framework, middleware
- domain: web-development, backend, apis, developer-tools
- platform: ruby
- tags: -api, rails, resource-oriented-api, sideloading, rest-api, web-server

## Member repositories
- graphiti-api/graphiti (main) score 100

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:12.517999+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:57:46.633077+00:00, confidence not recorded.
  - readme: https://github.com/graphiti-api/graphiti (fetched 2026-09-03T02:15:12.517999+00:00, sha 1a75fd7d75ae)
  - homepage: https://graphiti.dev/ (fetched 2026-08-29T12:59:18.933927+00:00, sha fb3ac2ef8749)
  - site_page: https://graphiti.dev/getting-started/installation (fetched 2026-08-29T12:59:18.939248+00:00, sha 2dc027ded60d)
- Data as of 2026-08-30T08:39:29.467469+00:00.