Fix schema contract issues
Connect
SPIRITT
GrafbaseGrafbase
Keep federated APIs accountable
Build Grafbase schema oversight, release evidence, and controlled access workflows from your connected graphs. Give SPIRITT the outcome and put your connected account to work.
What you can do with Grafbase.
Know the composed contract
Read federated and subgraph schemas, endpoints, and branch context before changing dependent apps.
Make checks actionable
Turn schema-check failures into precise engineering work with commit and validation evidence.
Control access deliberately
Review access tokens and apply explicitly scoped role or ownership changes with traceable decisions.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your Grafbase workflows, connected apps, and finished outcomes.
02
Connect Grafbase
Connect Grafbase and select the account and records your agent should work with.
03
Hand over a mission
Describe the result, scope, and handoffs. SPIRITT builds the workflow and follows the work through.
Hand over a mission.
Choose a mission. Make it yours.
Put Grafbase to work.
Keep federated APIs accountable
Questions
Grafbase, with SPIRITT.
01What can SPIRITT do with Grafbase?+
Build Grafbase schema oversight, release evidence, and controlled access workflows from your connected graphs. Read federated and subgraph schemas, endpoints, and branch context before changing dependent apps. Turn schema-check failures into precise engineering work with commit and validation evidence.
02Can SPIRITT build an app around Grafbase?+
Yes. Ask it to "build a schema operations desk". Build a Grafbase operations app from published subgraphs, branch-scoped composed schemas, and schema-check history. Route failures to GitHub owners with the check ID, error count, subgraph name, and commit metadata. Join diagnostics from the authorized repository CI result or a supplied diagnostic artifact before defining a precise repair, then track fixes and fresh check results.
03Can SPIRITT operate schema checks without inventing a deployment action?+
Yes. It reads existing checks, compares schema contracts, and carries fixes through a separately connected repository workflow. It re-reads check results for evidence. Subgraph deletion can be evaluated with a dry run before any separately authorized removal.
04How does Grafbase work with my other apps?+
Connect the apps your mission uses. GitHub to fix schema contract issues; GitLab to carry release evidence; Linear to own API change follow-up. SPIRITT carries the handoff through and checks the result in the destination.
05What should I know about the Grafbase connection?+
Grafbase connects published schemas, validation checks, notifications, access tokens, and specific role or ownership actions. Schema checks are permanent records. Gateway configuration belongs in its repository, and complete audit history may require an administrator-provided export.
06How do I get started with Grafbase?+
Open a SPIRITT workspace, connect Grafbase, and name the target records and desired outcome. Start with "Build a schema operations desk" or bring your own mission. Set the scope for changes and external actions, then let your agent run the work.