For Agents
Triage GlitchTip error issues, manage projects and teams, configure alerts, and read events from a Sentry-compatible error tracker.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GlitchTip API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with GlitchTip API.
Triage and bulk-update issues across an organisation via PUT /api/0/organizations/{org}/issues/
Resolve, ignore, or reopen a single GlitchTip issue by ID
Provision a new project under a team for a freshly deployed service
Read the latest event payload for an issue to diagnose a stack trace
GET STARTED
Use for: I need to mark a GlitchTip issue as resolved, List all unresolved issues for the production project, Get the latest event for a GlitchTip issue ID, Create a new GlitchTip project for a service we just deployed
Not supported: Does not page on-call engineers, manage source repositories, or run CI - use for error tracking, issue triage, project provisioning, and uptime monitoring only.
GlitchTip is an open-source error tracking and uptime monitoring platform that is wire-compatible with the Sentry SDK, so any Sentry-instrumented application can report errors to it without code changes. The GlitchTip API exposes the management surface around that data: organisations, teams, projects, issues, events, alerts, uptime monitors, and members. Use it to triage and resolve issues programmatically, provision projects for new services, configure alert rules, and maintain status pages alongside the rest of your developer tooling.
Configure uptime monitors and alert rules per project
Manage organisation members and team membership for access control
Patterns agents use GlitchTip API for, with concrete tasks.
★ On-Call Triage Automation
On-call engineers can reduce alert noise by automating triage: list unresolved issues for the org via /api/0/organizations/{org}/issues/, group them by fingerprint, then bulk-update with a single PUT call to resolve known-flaky tests or assign owners. The latest event payload is one call away via /api/0/issues/{issueId}/events/latest/, so the automation can attach a full stack trace to a Slack thread.
List issues with GET /api/0/organizations/{org}/issues/, filter by environment=production, then PUT the same endpoint with status=resolved for the matching IDs.
Project Provisioning for New Services
Platform teams provisioning a new microservice want a GlitchTip project created and DSN issued automatically. POST /api/0/teams/{org}/{team}/projects/ creates the project under the right team, and the response carries the DSN that the deployment pipeline injects into the service's environment. Provisioning takes seconds and avoids manual dashboard clicks.
POST /api/0/teams/{org}/{team}/projects/ with name=payments-svc and platform=python, then read the DSN from the response.
Issue Comment Bot
When a GlitchTip issue fires, an agent can post a comment with deploy context, recent commits, and a suggested owner. /api/0/issues/{issueId}/comments/ accepts text comments, so an LLM can summarise the latest event and leave a triage note inside the issue itself rather than in a separate Slack channel.
POST /api/0/issues/{issueId}/comments/ with a body summarising the latest event and the most likely owning team.
AI Agent Error Diagnosis
An agent connected through Jentic can answer engineer questions like "why is /checkout failing?" by listing recent issues for the project, loading the latest event for the top match, and proposing a fix. Because the spec is structured, the agent doesn't browse the GlitchTip UI - it calls /api/0/projects/{org}/{project}/issues/ and /api/0/issues/{issueId}/events/latest/ directly.
Search Jentic for 'list glitchtip issues', load the schema, and execute it for project=checkout, then fetch the latest event for the top result.
51 endpoints — glitchtip is an open-source error tracking and uptime monitoring platform that is wire-compatible with the sentry sdk, so any sentry-instrumented application can report errors to it without code changes.
METHOD
PATH
DESCRIPTION
/api/0/organizations/{org}/issues/
List issues for an organisation
/api/0/organizations/{org}/issues/
Bulk update issues
/api/0/issues/{issueId}/events/latest/
Get the latest event for an issue
/api/0/issues/{issueId}/comments/
Add a comment to an issue
/api/0/teams/{org}/{team}/projects/
Create a project under a team
/api/0/projects/{org}/{project}/
Get project details
/api/0/organizations/{org}/issues/
List issues for an organisation
/api/0/organizations/{org}/issues/
Bulk update issues
/api/0/issues/{issueId}/events/latest/
Get the latest event for an issue
/api/0/issues/{issueId}/comments/
Add a comment to an issue
/api/0/teams/{org}/{team}/projects/
Create a project under a team
Three things that make agents converge on Jentic-routed access.
Credential isolation
GlitchTip API tokens are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and the Authorization header is injected at execution time, so the raw token never appears in the agent's context.
Intent-based discovery
Agents search Jentic by intent ('list unresolved issues', 'create glitchtip project') and Jentic returns the matching GlitchTip operation with its JSON schema, so the agent calls the right endpoint without reading the GlitchTip docs.
Time to first call
Direct GlitchTip integration: 1-2 days for token handling, pagination, and bulk-update logic. Through Jentic: under an hour - search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using GlitchTip API through Jentic.
What authentication does the GlitchTip API use?
GlitchTip uses an API key sent in the Authorization header (scheme tokenAuth, type apiKey). Generate the token in your GlitchTip account settings. Through Jentic the token is held in the vault and not exposed to the agent.
Is the GlitchTip API compatible with the Sentry SDK?
Yes for ingestion - GlitchTip accepts events from the Sentry SDK, so existing instrumentation reports without code changes. The management API documented here (organisations, projects, issues) is GlitchTip-specific and does not mirror Sentry's management surface verbatim.
What are the rate limits for the GlitchTip API?
GlitchTip's hosted plan applies per-account quotas rather than fixed per-endpoint limits, and self-hosted instances have no enforced limits. Inspect HTTP 429 responses from app.glitchtip.com when running bulk issue updates and back off accordingly.
How do I bulk-resolve issues through Jentic?
Search Jentic for 'bulk update glitchtip issues', load the schema for PUT /api/0/organizations/{org}/issues/, and execute with status=resolved and the list of issue IDs in the body. Run pip install jentic to start.
Can I create projects programmatically when a new service ships?
Yes. POST /api/0/teams/{org}/{team}/projects/ creates a project under the named team and returns the configuration including the DSN that your deploy pipeline injects into the service.
Does GlitchTip charge for API calls?
GlitchTip's pricing is event-based (errors and transactions ingested), not API-call-based. Management API calls do not count against your event quota; only events ingested through the Sentry-compatible endpoint do.
/api/0/projects/{org}/{project}/
Get project details